-
Notifications
You must be signed in to change notification settings - Fork 34
Introduce isomorphic testing #197
Copy link
Copy link
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif:hardHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantkind:maintenanceWork required to avoid breaking changes or harm to project's status quoWork required to avoid breaking changes or harm to project's status quotype:issue
Description
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps updif:hardHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantkind:maintenanceWork required to avoid breaking changes or harm to project's status quoWork required to avoid breaking changes or harm to project's status quotype:issue
Currently, tests are split into browser (
*.browser.spec.ts) and node (*.spec.ts) tests. This introduces tests duplication and mainly it resolves in small coverage in browsers.Using isomorphic testing leads to writing only one set of tests that is shared between all tested environments.