Separate test runs for Unit versus Integration

Open
#6,834 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd, developer-experience, testing

Research direction

Start by inspecting the current GitHub Actions CI setup and the Nox or Pixi entry points used for local runs. Separate core-only unit tests from core-plus-optional-dependency integration tests, account for the three SPEC-0 Python versions and built-wheel imports, and verify that the split works in CI and locally.

Written by the indexing model from the issue text.

Description

Dragon Sub-Task 🦎
  • Unit test run: runs using core dependencies only
    • Runs against the 3 SPEC-0 Python versions (so will need locked env specs for each)
  • Integration test run: runs using core and optional dependencies
    • Runs against only the latest SPEC-0 Python version, to save resource (could we run against all 3 for the lock update PRs only?)
  • Split should ideally be easy to run in CI AND locally (i.e. Nox or Pixi). At minimum the GHA CI should be split

(Need to think about testing built wheels too. Currently we just test import, and that is against all 3 Python versions)

Dominant language
Python
Stars
724
Forks
317
Avg merge
3d 20h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SciTools/iris

All issues in SciTools/iris

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.