-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fixture phases should be processed in order #6
Comments
Temporary fix was to enumerate the tests in order in |
0963158 has a better solution.
|
Not yet relevant, but the ordering of the phases depends on how
unittest discover
does things. Ideally, we want the phase tests to be run in the order of dependency within the compiler (ex. scanner -> parser -> semantic analysis -> etc.). In this way, if the compiler under test has a bug in an earlier phase we don't test a later phase first (and mislead the user that the error occurred in the later phase).The text was updated successfully, but these errors were encountered: