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
Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Currently there are zero unit tests for the JavaScript components of the code, which is ... not good.
First priority is setting up some unit test framework and integrating it into the CMake build process. Most likely candidate is QUnit, since it supports unit tests involving the DOM, which most other frameworks do not. Performing unit tests automatically, instead of going through a web browser each time, will probably require node.js components in some way.
Originally reported by: Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann)
Currently there are zero unit tests for the JavaScript components of the code, which is ... not good.
First priority is setting up some unit test framework and integrating it into the CMake build process. Most likely candidate is QUnit, since it supports unit tests involving the DOM, which most other frameworks do not. Performing unit tests automatically, instead of going through a web browser each time, will probably require node.js components in some way.
Possible alternatives:
* Testing DOM JavaScript Functions with Mocha
* JavaScript DOM in browser tests with Mocha & Chai
* Testing JavaScript with PhantomJS (actually recommends Mocha for DOM-based tests)
Actually creating some unit tests will likely be a longer and more involved process, but it won't get done without laying the foundation first.
The text was updated successfully, but these errors were encountered: