javascript-testing | Introducción a los tests con javascript guiada por | Runtime Evironment library

I'm trying to write a unit test for a method and I'm having some trouble getting things to run smoothly.

I need to test the only public method in this class, AuthenticateAdminService.authAdmin, which makes calls to the private methods, which make calls to third party libraries like jsonwebtoken and bcrypt. The prolem I'm running into is when I try to compare passwords with bcrypt it returns as false during automated-tests but true during manual-testing.

How am I supposed to reliably mock these private methods and libraries? I found a few posts here on SO that did nothing for me, perhaps I just didn't understand the answers. I found this post on mocking libraries which really helped for a moment until I realized that any library I'm using is wrapped inside a private method which does me no good in my tests as I'm not directly calling the mocked library.

I think I'm supposed to create a mock of the AuthenticateAdminService class private methods. Test the actual public method, authAdmin, and somehow get the mocked private methods called instead of the real versions. Any help?

We're using Chrome headless with Capybara and Selenium for three js feature tests.

We're having a predictable (only on CI) failure when one specific js test (using xhr) follows another which also uses xhr (see https://github.com/thredded/thredded/tree/separate-out-js-from-non-js-in-ci for the code or https://travis-ci.org/thredded/thredded/jobs/302376004 for a sample run).

The server error is always being surfaced in the next spec "User creates new topic with title and content" but the url is evidently from the previous spec "User replying to a topic starts a quote-reply (js)".

The obvious thing is that there is a race condition between a request that falls off the end of the spec and happens after DatabaseCleaner.clean. However, my understanding is that with Capybara 2.7+ [1] after_each should happen after a reset_session! which should prevent this precise problem. In any case I am pretty sure there is nothing in the page that could be creating this request (we have a specific wait/test for the completion of this ajax request).

This is happening with 3 different databases and 3 different rails versions (4.2, 5.0, 5.1). We've upgraded to latest Capybara.

Have tried disabling turbolinks, adding in a massive (10s) sleep at the end of the offending spec... Have tried manually resetting sessions too.

Must be missing something. Any pointers?

[1] https://github.com/teamcapybara/capybara/pull/1637 referenced from https://bibwild.wordpress.com/2016/02/18/struggling-towards-reliable-capybara-javascript-testing/

UPDATE: Have added references to xhr, as another (new) js spec is having the problem, and that it isn't the first two requests (login form, and post to login) that is surfacing the error, but the first xhr request that surfaces the error. In the new case the xhr that is getting requested is being requested with POST in the subsequent spec even though it was originall requested with GET

I am trying to write unit tests for a function that reads a jsonfile into an object. I read the file with