You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wkurniawan07 opened this issue
Apr 3, 2018
· 1 comment
Labels
a-TestingTesting-related traits such as efficiency, robustness, coveragec.DevOpsProcess-related or build-related improvement and additionp.HighSignificant impact; would like to do in the next few releases
To support browser-based QUnit tests like we are doing now, we have to bundle all the test files (and also production files) into one with Webpack, run all tests together, and read the test report including coverage. This workflow has many drawbacks (and it doesn't help that our JS code has almost 100% coupling to the DOM structure):
There is no way to run a single unit test
The "coverage" reported includes the extraneous codes added by Webpack
The fact that we need to bundle the test files and have the dev server up before running the tests means (unnecessary) extra effort spent
We need a new test framework which (1) allows single test runs and (2) does not necessitate bundling.
The text was updated successfully, but these errors were encountered:
wkurniawan07
added
p.High
Significant impact; would like to do in the next few releases
a-Testing
Testing-related traits such as efficiency, robustness, coverage
t-JS
c.DevOps
Process-related or build-related improvement and addition
labels
Apr 3, 2018
a-TestingTesting-related traits such as efficiency, robustness, coveragec.DevOpsProcess-related or build-related improvement and additionp.HighSignificant impact; would like to do in the next few releases
To support browser-based QUnit tests like we are doing now, we have to bundle all the test files (and also production files) into one with Webpack, run all tests together, and read the test report including coverage. This workflow has many drawbacks (and it doesn't help that our JS code has almost 100% coupling to the DOM structure):
We need a new test framework which (1) allows single test runs and (2) does not necessitate bundling.
The text was updated successfully, but these errors were encountered: