2 ms·
> So why do we want this? Just yesterday, I ran into an issue where a set of node unit tests were failing. My college and I were both getting failures, but dif
by falcolas 6y ago
> So why do we want this?
Just yesterday, I ran into an issue where a set of node unit tests were failing. My college and I were both getting failures, but different failures. The reason was: Different versions of Chrome, and thus different versions of the chrome integration plugin.
Given that we have effectively no control over Chrome's auto-updates, we'll never have truly identical development environments. A container with headless chrome would have resolved this for us.
- marcus_holmes 6y agoBut your customers still have widely varying versions of Chrome. So while your test might work, your code is still broken. Or did I misunderstand?
- falcolas 6y agoIt's purely a test fixture setup that's failing because of a need for lockstep Chrome and the Chrome test fixture versions in Node. So, the code isn't broken for customers, just the local testing story.