-
Notifications
You must be signed in to change notification settings - Fork 1
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 actual result checks to test suite #63
Labels
Comments
To do after #33. |
cwmeijer
added a commit
that referenced
this issue
Feb 16, 2021
Closed
cwmeijer
added a commit
that referenced
this issue
Mar 2, 2021
The challenge here is to have the experiments return sensible results for the user while also meaningfull to test against (sensitive to code/logic changes). This commit manages to do this for most tests. refs #63
cwmeijer
added a commit
that referenced
this issue
Mar 2, 2021
cwmeijer
added a commit
that referenced
this issue
Mar 2, 2021
cwmeijer
added a commit
that referenced
this issue
Mar 2, 2021
cwmeijer
added a commit
that referenced
this issue
Mar 3, 2021
fixed in #78 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, our CI test suite of running experiments is only a "smoke test", i.e. it checks only whether everything runs, but not if it runs correctly. We should add result value checks so that we can see when changes in code change model outcomes.
The text was updated successfully, but these errors were encountered: