Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore new JavaScript test framework #8749

Closed
wkurniawan07 opened this issue Apr 3, 2018 · 1 comment
Closed

Explore new JavaScript test framework #8749

wkurniawan07 opened this issue Apr 3, 2018 · 1 comment
Labels
a-Testing Testing-related traits such as efficiency, robustness, coverage c.DevOps Process-related or build-related improvement and addition p.High Significant impact; would like to do in the next few releases

Comments

@wkurniawan07
Copy link
Member

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.

@wkurniawan07 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
@wkurniawan07 wkurniawan07 added this to the V7.0.0 milestone Aug 14, 2018
@wkurniawan07 wkurniawan07 modified the milestones: V7.0.0, V7.0.0-alpha.0 Nov 20, 2018
@wkurniawan07
Copy link
Member Author

Resolved in V7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-Testing Testing-related traits such as efficiency, robustness, coverage c.DevOps Process-related or build-related improvement and addition p.High Significant impact; would like to do in the next few releases
Projects
None yet
Development

No branches or pull requests

1 participant