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

Unit tests for JavaScript #37

Open
mbollmann opened this issue Aug 14, 2015 · 2 comments
Open

Unit tests for JavaScript #37

mbollmann opened this issue Aug 14, 2015 · 2 comments
Labels

Comments

@mbollmann
Copy link
Member

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:

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.


@mbollmann
Copy link
Member Author

Original comment by Marcel Bollmann (Bitbucket: mbollmann, GitHub: mbollmann):


We could also include sth. like JSLint in CMake's lint target.

mbollmann pushed a commit that referenced this issue Mar 18, 2017
Add support for frontend tests (#37)
@mbollmann
Copy link
Member Author

Basic support for JS unit testing has been introduced in #92. Tests of course still need to be actually written...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant