Skip to content

Consolidate test suite #268

Description

@ms609

Look for:

  • Duplicated tests
  • Stale objectives - testing functionality that's retired, or A = A
  • Misnamed files
  • Stepping stone tests: e.g. "does change A to the plumbing introduce new errors" is redundant; if change A has happened, then the question is "are there errors in the end result", and all tests of that belong together.

The guiding principle is one test file per source file. Exceptions are tests that capture larger processes that span multiple functions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions