-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add tests to the repo #75
Comments
eagle eye! 😉 But I did not write any test automation. I will put them into an own branch for now and we will see whether it helps or whether someone wants to use them for something more useful. 😁 |
I took a brief look at the
It is then trivial to write a Makefile that treats each directory name as a target name, so when you run |
The problem I see, is, that the html can change but the result still be valid. But I guess you can easily adjust the testcases if need. 🤷 So, I myself will not find the spare time for this. If you want to contribute this, feel free! 😃 |
I'd suggest making the tests run on an intermediate representation consisting of the characters and the state of each. This would help test the part more likely to break (the parser) and avoid changes that only affect the state to html conversion. Additionally a separate set of tests could be added for testing state to html translation |
Looking at .gitignore, there's this line:
which hints that some tests have been written for the program, but are excluded from the repository.
It would be useful to have these tests as part of the repo.
The text was updated successfully, but these errors were encountered: