Baptiste Mathus 2ad08058a9 *Now* the test does test what I wanted it to... ... Basically, I wrote the successive then and catch like every steps were going to be gone through. But obviously, this is not how Promises work: if a 304 is thrown at the first line, it was going to the last catch directly, making the test succeed, but absolutely not testing the intended use case.		2018-10-12 15:53:04 +02:00
..
fixtures/53318	This time fix the update service behavior when considering a flavor for real	2018-09-16 16:47:20 -07:00
services	Add expect calls to check things look actually good	2018-10-09 22:52:50 +02:00
app.test.js	Refactor server-side authentication to rely more heavily on @feathersjs	2018-09-13 10:37:04 -07:00
helpers.js	Refactor server-side authentication to rely more heavily on @feathersjs	2018-09-13 10:37:04 -07:00
rand-patch.js	Refactor the acceptance tests into their own directory to speed local development	2018-04-05 16:54:28 -07:00
update-versions.test.js	*Now* the test does test what I wanted it to...	2018-10-12 15:53:04 +02:00