Files

T

Travis b73cf2e272 Adding tests to prove expected behavior around force starting a quest (#7848 )

* starting

* adding tests to prove the expected behavior occurs around force starting a quest. part of #7653

* fixing up tests and adding functionality to remove user from quest if they are not in the questing party

* adding code to handle when the user is deleted and added a test around that situation

* fixing up comments

2016-09-10 23:10:37 -05:00

integration

Adding tests to prove expected behavior around force starting a quest (#7848 )

2016-09-10 23:10:37 -05:00

unit

Collection quest progress reports "found no [item names]" fixes #7816 (#7883 )

2016-09-10 23:03:28 -05:00

README.md

API v3 [WIP] (#6144 )

2016-05-23 13:58:31 +02:00

README.md

How to run tests:

npm test is equivalent to gulp test:api-v3 which will run, in order, gulp lint, gulp test:api-v3:unit and gulp test:api-v3:integration. If one of these fails, the whole npm test command blocks and fails. Each of these commands can also be run as a standalone command.
To run the server and the integrations tests in two different terminals (to better inspect the output in the server) run npm start in one and npm test:api-v3:integration:separate-server in the other