Does anyone have experience with modifying Jest to run in a browser instead, similar to how Karma works?
-
-
Prikaži ovu nit
-
Note that I have nothing against JSDom and I am not claiming it is lacking features. However, we would like to run our tests in the environment the actual production code runs in. By only running in JSDom, we would miss subtle differences between different browser implementations
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
How many of those subtle differences have you caught with your karma test suite?
-
We caught issues where our polyfills were subtly incorrect/had limitations we weren't aware of. Also layout scheduling and `requestAnimationFrame` could be different. Lastly, we saw our Workers being killed on Safari, but not in Chrome. Probably related to memory consumption.
- Još 4 druga odgovora
Novi razgovor -
-
-
What kind of differences are you speaking of? Jsdom tries to stick as much as possible to the specifications.
-
The difference in browser environments. E.g. Firefox, Safari and Chrome all can have subtle differences, even though they are implementing the same standards. We would like to write tests to catch these issues.
- Još 2 druga odgovora
Novi razgovor -
-
-
Considered making a pull request to implement the feature? Seems equally efficient, and is a nice gesture to the rest of us who are using jsdom!
-
We want to run tests in the environment the actual code will run. This would include multiple browser environments, which can and do have subtle differences. If we would only test in JSDom, we would not catch these issues.
- Još 3 druga odgovora
Novi razgovor -
-
-
Jest is the worst
- Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.