* Updated collection quest tests for no found items.
Single-item quests state [user] found no [items]. instead of [user] found nothing. If a
quest has two items, the chat message is [user] found no [item1] and no [item2].
* Collection quest messages changed from [user] found nothing to [user] found no [item]
* Tests for no collection quest items found changed to [user] found 0 [item1], 0 [item2]
* Changed chat messages for no found collection quest items to [user] found 0 [item1], 0 [item2]
* Sort items alphabetically in multi-item quests so that it always returns the same string
* Formatting updates to conform to test specifications (for collection quest progress reports with no items found
* Simplified handling of items not found: any items not found are added to the list of found items with quantity 0 for reporting in the group chat. This also causes all items to appear, in the list, even if only one type is found in a multi-item quest.
* Test the group chat message when no items are found in multi-item quests. Test succes no longer depends on the order items are listed.
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
Alyssa Batula
923b6c495e