Test suite needs expanding
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 16
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Currently the CI only runs what amounts to test 3. GitHub Actions gives us ~2000 minutes per month for CI and the max runtime of a single container is ~hours.
I'd suggest perhaps switching back to either the "long" CI test or running tests 1 through 3. As long as total test time stays under an hour we should be fine, even during fairly heavy development bursts... ideally we'd run our different tests in parallel and then check test status based on whether they all pass (e.g., the way SpacePy does it)
It's also a good idea to plan out proper unit tests, but expanding the coverage of our regression and integration tests is the low hanging fruit.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the GitHub Actions configuration and the existing test 3, long CI test, and tests 1 through 3 referenced in the issue. Determine which test selection or parallel arrangement keeps total CI time under an hour, and consider the work done when the selected regression and integration tests all run and report their combined status successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran, github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100