feathers-chat | A Feathers real-time chat application | Frontend Framework library

So I downloaded and ran the repo, I used VSCode to run the app and set break points. I created a breakpoint in the before create hooks on users.

The issue here is that the gravatar hook is expected the email to be context.data but it is in fact embedded within the facebook response. You will need to look at extracting the email from that data so that you can create a gravatar or just remove the gravatar hook altogether.

if it is common practice to use an in-memory database for a test environment, instead

Sadly it is a common practise, but not particulary good one. When you use different database for testing and other for production your tests are actually not testing that the application code is working in real database.

Other negative effect is also that you cannot use special features of any of those databases, but the code would have to use that subset of DB features, which are supported by both of the databases.

I would ran all the tests with all the supported real databases to actually make sure that code works on every targeted setup.

ps. Someone was telling to use mocks for abstracting database... that is another bad practise. They work for some small part of testing, but in general case you need to run tests against real database to be sure that code works correctly. Important thing is to setup tests in a way that you have a fast way of truncating old data and populating new test data in.

It's an issue with generator-feathers

Remove the rethinkdb object from config/default

will see if I can fix the main problem

Edit: Fixed

When I actually created a user, the issue no longer occurred. I

• created a user
• logged in successfully
• attempted to log in as a user that does not exist.

When I performed the last step, the authenticate Promise was rejected as expected, but my browser no longer claimed I wasn't catching the exception.

Turns out there is a bug in the feathers-cli@2.2.2, I uninstalled and installed version 2.1.1 and I had no more problems. Will inform of this error.