-
Notifications
You must be signed in to change notification settings - Fork 816
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
Improve Testing #7
Comments
Hi Martin, I've created a test-externs branch with an idea for a testing strategy. It uses processing-js as an example because it was requested in #18 and also because processing-js has a comprehensive reference test suite. This branch's build.boot introduces a As it stands, only the test code is processed by the google closure compiler. The processing-js library itself is linked as an external library in the test suite. I don't think the processing-js code is compatible with advanced-optimizations and would have to be included as a foreign-lib. The externs ensure that client code is compatible - this testing strategy has already highlighted an error and some omissions in the file pulled from quil/processing-js. List of Steps
Limitations / Further Work
I'd be very interested in your (and others') thoughts on this as a general approach to testing externs files. If you think this might be a useful package to add to cljsjs, I'd be happy to open a PR. |
Fixed some typos in README.md.
All of these packages should go through some basic testing before being published.
I started a very simple approach in the testbed project but as @Deraen noted this is probably better be done as part of packaging within this repository.
The text was updated successfully, but these errors were encountered: