What is Jasmine?
Who uses Jasmine?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Jasmine in their tech stack.
For our internal team and collaboration panel we use Nuxt.js (with TypeScript that is transpiled into ES6), Webpack and npm. We enjoy the opinionated nature of Nuxt.js over vanilla Vue.js, as we would end up using all of the components Nuxt.js incorporates anyways and we can adhere to the conventions setup by the Nuxt.js project, which allows us to get better support in case we run into any dead ends. Webpack allows us to create reproducable builds and also debug our application with hot reloads, which greately increased the pace at which we are able to perform and test changes. We also incorporated a lot of testing (ESLint, Chai, Jasmine, Nightwatchjs) into our pipelines and can trigger those jobs through GitLab CI. All packages are fetched through npm, so that we can keep our git repositories slim and are notified of new updates aswell as reported security flaws.
Switched from Jasmine with Karma that come setup by Angular CLI to use Jest instead, since Jasmine and Karma were very finicky in my setup and had to be reconfigured frequently to run tests properly.
Jest was also easier to integrate into my workflow with Visual Studio Code.
I write unit tests with Jasmine, and use nodejs Jasmine as a test runner. Jasmine
We use Jasmine for all our front-end web interface tests. Works great for testing all our Angular components. Jasmine