-
-
Notifications
You must be signed in to change notification settings - Fork 828
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
tests: Add known_failure as a test option, and migrate many tests to it #12324
Conversation
Hmm, this name implies to me that a given test is a "negative test" and that the expected result (ie. when Ruffle is working correctly) is that it fails. Sure, the message it gives explains that this is not the case, but in the test itself it's not there. How about "known_fails" (or something similar)? I like the basic idea though! |
I just took the name Adrian said and rolled with it, didn't give much thought. Happy to change it! |
Excellent IMHO! |
…ass on my machine
Renamed! |
The goal is to use
known_failure = true
instead ofignore = true
for tests that we know don't work now, but may work one day.When a test is marked
known_failure
, it'll be tested and the comparison logic is inverted. If it suddenly passes, it'll throw an error and the developer will be prompted to unflag it as the test now passes and should be checked going forwards for regressions.