You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 14, 2022. It is now read-only.
Is the swagger module itself listed as a dependency in your package.json (and not only e.g. the swagger-express-mw module) ?
If I remember correctly I had this one too when deploying to Travis CI and could fix it by adding the swagger module (as a locally installed dependency ... and thus in the PATH) in my package.json.
Ok @Bolein, I (personally) don’t see that point, but of course I do not know your project .. so never mind. Then, I guess, you can try installing the swagger-cli module only, but I suppose this (alone) probably will not work.
Independent of swagger-node capabilities you might best go for „standard“ npm features (like configuring a test script in the scripts section of your package.json, e.g. node /path/to/test.js) or Travis CI features (like configuring the before_script and script stage according to your needs with default shell commands).
Anyway, for everybody else coming across this issue and deciding to go for swagger project test, keep in mind that there is still an open issue with its exit code: #288
I'm trying to deploy my app through Travis CI, but it fails the test phase because of the error:
Is there a way to run the tests without having the swagger module installed on the remote machine?
The text was updated successfully, but these errors were encountered: