Testing CI with small e2e test.#224
Conversation
|
@Cam-Wheeler is attempting to deploy a commit to the lalithshiyam's projects Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a GitHub Actions CI workflow for automated testing of the MOOSE project. The workflow sets up the test environment, installs dependencies, and runs a basic end-to-end test across multiple Python versions to verify the core segmentation functionality works correctly.
- Adds a new CI workflow that runs on pushes and pull requests to the main branch
- Implements an initial end-to-end test that validates basic MOOSE segmentation on CPU
- Updates the release workflow description to clarify build dependencies
Reviewed Changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/testing.yml |
New CI workflow that tests MOOSE across Python 3.10-3.14 using pytest on the basic e2e test |
tests/test_e2e.py |
New end-to-end test that executes MOOSE segmentation with clin_ct_organs model on sample CT data |
.github/workflows/release.yml |
Clarifies step name from "Install dependencies" to "Install build dependencies" |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@Cam-Wheeler you are wonderful, many thanks for prepping this. I am all in for this contribution. let me quickly review this, copilot's review as rather...aesthetic. |
|
@Keyn34 as discussed, please take this over. |
|
Thank you @Cam-Wheeler! I am reviewing this now and will let you know if I have any more questions. |
|
@Cam-Wheeler thanks again for introducing this! I merged it, as you can see. Just wanted to thank you once more. :) |
|
Awesome! Thank you very much @LalithShiyam and @Keyn34! Ill be pulling in some more unit tests as I make them! Looking forward to speaking again! |
Hello MOOSE team,
This pull request introduces a workflow for basic unit testing into your CI pipeline. Just wanted to guage your interest in this!
What's Included:
A new .yaml file that sets up MOOSE and its dependencies before running unit testing. The tests run across recent Python versions, starting from 3.10+. Currently, the workflow only includes a minimal end-to-end test to confirm the setup and basic execution without errors. The unit tests are configured to run prior to your Vercel approval/release step so it can improve confidence before you press the approval button!
I've also included a minor, non-functional update to release.yaml for clarity, explicitly separating the unit testing and building phases in the workflow description.
The small size of the PR is to make your initial review easy. If you think this is a valuable direction, I can submit subsequent PRs that each introduce a small, manageable batch of unit tests to minimise the review effort. If unit testing is not a priority right now, no problem! If you like the idea, any comments on preferred structure or implementation details would be greatly appreciated.
Thanks!!!
Cam