svelte-jester VS javascript-testing-best-practices

svelte-jester: precompiles Svelte components before tests.

I’m using jest with svelte-jester and @testing-library/svelte.

While I mentioned in the beginning of the article that I am relatively happy with the current state of my reference TypeScript monorepo template, I still think there are a couple of things that can be improved. Chiefly I think that Yarn 2 (‘Berry’) is still not as mature as I would like it to be. Support for ESM for instance would be awesome, the lack of which caused me some problems in trying to make Svelte work within the monorepo. However, I think it is very worthwhile what the Yarn team attempts to achieve with Yarn 2 and I am happy to support it by trying to make it work in the monorepo template.

I need to test some components that require svelte-spa-router by using jest. Well the problem is, an import from svelte-spa-router causes the error on my previous successful tests. Came across this kind of issue on github https://github.com/mihar-22/svelte-jester/issues/7 and try to replicate the solution like this.

😎 You want to take your JS testing skills to the next level, here is a nice repo -> javascript-testing-best-practices

Surprised nobody referred this

Yoni Golberg's JavaScript Testing best practices guide is always a good resource to consult, for both beginners and experienced developers: https://github.com/goldbergyoni/javascript-testing-best-practices

I really like how testing is done in Rails. Why did you choose the snapshots approach? I never have seen it for this purpose, they say it's bad practice even for the frontend (check testing practices for node btw), so, why?

JavaScript Testing Best Practices, by Yoni Goldberg is a GitHub repository. It gives good practices about testing.