-
Notifications
You must be signed in to change notification settings - Fork 18
Add CI for regression tests #25
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 CI for regression tests #25
Conversation
…ns/k-wave into sp/improve_CI_output_2
For testing the workflow
…sult display functions
(these were commented out for testing purposes)
…egression_tests
bencox
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very useful, thank you.
I realised that when you open the CI output (if it has failed) it directs you to the end of the output, so it makes more sense to put this information at the end after all
|
Thanks @bencox! I made one last tweak. I realised the CI output opens at the bottom when it fails, so it actually makes more sense to put the most important info (N failed / passed & failed tests) at the end. I’ll merge once I’ve confirmed the CI output looks right. |
What does this PR do?
Resolves #23 by running the regression tests in the GitHub Actions workflow.
Generalises
runUnitTestsfunctions for reuse with regression tests.runUnitTests_show_results->show_test_resultsrunUnitTests_create_artifact->save_artifactRuns regression and unit tests in the same workflow to create a clear overview
unit_tests.yml->run_tests.ymlSee the new CI output here.
Linked issues
#9 #23
Notes
Adding both the unit and regression tests to the same
run_tests.ymlmakes theymlfile a little bit more unwieldy but results in a much nicer CI output compared to seperating them. I tried to avoid some of the repetition in theymlfile with the use of anchors but decided the code was clearer as it was without anchors.