By object of testing:
- unit tests — testing only one class/function, mocking all its dependencies;
- integration tests — testing several units at a time within the same project. Usually, in implies mocking of input data, like API calls;
- e2e tests — testing of the product. Usually is performed on the
predefined DB snapshot, might test at the same time several
projects/modules (API,
ftw,widgets-routesetc. - pixel-perfect — by-pixel comparison of the rendered page
- snaphot testing — comparisong of the generated by component html-code, which allows to find missing data or any changes.
By the environment:
- browser tests — are executed in the browser, oftenly with Karma or
Puppeteer. Allows to test how components are builded/rendered in the
browser, with native support of browser globals and
events. Often executed on the headless versions of browsers, which
improves performance. Our
widgets-ssrmodule is builded in the similar fashion - Node.JS tests — all globals are mocked with dummies/polyfills, tests are executed poorely with NodeJS. It’s fast, but might result in problems with environement or missing some issues that might appear in the browser.
- dom interactions are relatively complicated to test, but still possible with Jest.
- code, that works fine but have to be refactored;
- bugs, that has been reopened after change in related component/service;
- business-logic parts
- Playwright integration with Jest
- jes-fn-pug
- Playwright, selectors and Shadow DOM from Ingvar
- node runner by Øystein
- ftw branch