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
This issue mainly serves as a discussion for adding more cases in the system tests, starting from the release_test test suite.
release_test
The test suite is specified in https://github.com/precice/tutorials/blob/develop/tools/tests/tests.yaml. We currently have:
We should still test the following.
These cases are either commonly encountered by users, or they test important features.
We don't want to test very long cases yet. The plan is to eventually restrict them to some first time steps. These are:
We cannot compare reference results for cases that were not there in the previous distribution release or that had different setups:
The text was updated successfully, but these errors were encountered:
We should also make a table of test cases x components/features, to discover blind spots on what we are not testing.
Sorry, something went wrong.
MakisH
No branches or pull requests
This issue mainly serves as a discussion for adding more cases in the system tests, starting from the
release_test
test suite.The test suite is specified in https://github.com/precice/tutorials/blob/develop/tools/tests/tests.yaml. We currently have:
We should still test the following.
First priotiry
These cases are either commonly encountered by users, or they test important features.
Later
Very long cases
We don't want to test very long cases yet. The plan is to eventually restrict them to some first time steps. These are:
Cannot be tested in v2
We cannot compare reference results for cases that were not there in the previous distribution release or that had different setups:
The text was updated successfully, but these errors were encountered: