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

Automated testing #2

Closed
SReichelt opened this issue Jan 27, 2019 · 0 comments
Closed

Automated testing #2

SReichelt opened this issue Jan 27, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@SReichelt
Copy link
Owner

Determine a framework for automated tests, and develop some tests that are particularly quick to implement. Ideas:

  • Read and rewrite the entire library, and compare with repository. The read/write functionality already exists as src/scripts/tidyLibrary.sh.
  • Render the entire library as text, and compare with previously accepted result. Would require a "blind" acceptance after every library change, but would likely catch errors when working on rendering code.
  • A generic black-box test for the VSCode language extension would be nice. https://code.visualstudio.com/api/working-with-extensions/testing-extension describes how to write unit tests, but it seems cheaper to query the extension for all links/tooltips/codelenses/etc. in a file and dump them, to detect unwanted changes.
  • The desktop version had unit tests for the type checker, based on a separate miniature library. These should be converted to TypeScript, and the library could also be used as a starting point for rendering tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant