Skip to content
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 a CI Workflow for System Tests #2062

Open
john-science opened this issue Jan 22, 2025 · 0 comments
Open

Add a CI Workflow for System Tests #2062

john-science opened this issue Jan 22, 2025 · 0 comments
Assignees
Labels
ci Related to continuous integration / github actions testing Related to tests

Comments

@john-science
Copy link
Member

ARMI provides some end-to-end tests in the form of Jupyter notebooks, that are run during unit testing. They serve several purposes, among them they are examples in the docs that we want to make sure are still working.

But they also serve as some end-to-end tests, the best ARMI can do without external physics kernels. As such, we should move them into their own CI channel, so we can see them on their own.

class NotebookTests(unittest.TestCase):
def test_runParamSweep(self):
runNotebook(os.path.join(TUTORIALS, "param_sweep.ipynb"))
def test_runDataModel(self):
runNotebook(os.path.join(TUTORIALS, "data_model.ipynb"))
# Do some cleanup because some code run in the notebook doesn't honor the
# TempDirectoryChanger
os.remove(os.path.join(TUTORIALS, "anl-afci-177.h5"))

NOTE: This would also be a good time to move these data files to armi/testing/resources/ or something similar.

@john-science john-science added ci Related to continuous integration / github actions testing Related to tests labels Jan 22, 2025
@john-science john-science self-assigned this Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Related to continuous integration / github actions testing Related to tests
Projects
None yet
Development

No branches or pull requests

1 participant