We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Author Name: Volker Stolz (Volker Stolz) Original Redmine Issue: 123, https://envisage.ifi.uio.no:8080/redmine/issues/123 Original Date: 2014-01-29 Original Assignee: Volker Stolz
Right now, we run e.g. the deadlock checker on models where it doesn't actually make sense, like an open system or one without main block.
Can we capture these preconditions in the unit tests somehow, so that they do not show up as failed? I guess it will come up more frequently.
So either we return to individual tests, or we somehow add this to the parametrised test runner...
The text was updated successfully, but these errors were encountered:
Original Redmine Comment Author Name: Volker Stolz (Volker Stolz) Original Date: 2014-02-10T11:55:50Z
Some tests now have preconditions, some more may be required.
Unfortunately, Bucky gets in the way: http://www.eclipse.org/forums/index.php/t/642964/ The views-count on my questions is already quite high, yet no answers.
Sorry, something went wrong.
we strive for no test failures and use Assume* in the tests as appropriate; closing
Assume*
No branches or pull requests
Author Name: Volker Stolz (Volker Stolz)
Original Redmine Issue: 123, https://envisage.ifi.uio.no:8080/redmine/issues/123
Original Date: 2014-01-29
Original Assignee: Volker Stolz
Right now, we run e.g. the deadlock checker on models where it doesn't actually make sense, like an open system or one without main block.
Can we capture these preconditions in the unit tests somehow, so that they do not show up as failed? I guess it will come up more frequently.
So either we return to individual tests, or we somehow add this to the parametrised test runner...
The text was updated successfully, but these errors were encountered: