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.

Sign up for GitHub

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

Jump to bottom

Automate compiler error testing #73

Open
CharlyCst opened this issue Aug 5, 2020 · 1 comment
Open

Automate compiler error testing #73

CharlyCst opened this issue Aug 5, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@CharlyCst
Copy link
Owner

Why?

The size of the code-base is growing quickly, our current end-to-end tests only covers successful compilation an thus we have no way to track regression on code that fail to compile.

How?

A nice way to test error messages would be to use some sort of snapshot testing cli tool, so that one can compare the previous and new output.
If no such tool exists, it could be worth trying to build one as a sub-project.
@CharlyCst CharlyCst added the enhancement New feature or request label Aug 5, 2020
@CharlyCst
Copy link
Owner Author

Linking to #18.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CharlyCst