Skip to content

tests: add coverage to headless units #511

@bjacobgordon

Description

@bjacobgordon

Phases

  1. pre-requisites
  2. Perform "vertical attack" to gauge checkpoints:
    1. Take easiest functional unit from "nothing" to "covered": library/math -> greatestCommonDivisor
    2. Take easiest class from "nothing" to "covered": NonTrivialString
      • prep directory to allow separation of test suites, performing useful refactors prior to creating any test suites
      • stub empty class-based suite
      • seed test template for class-based suite
      • stub complete coverage outline with it.todo
      • cover parsing rejection of empty strings
      • cover parsing rejection of null inputs in nullable parser
      • clarify error messages for parsing failures
      • cover successful parsing of valid strings
      • cover nullableParsedFrom success scenarios
      • cover equality comparison behavior
      • cover instance concatenation
      • cover static concatenation
      • cover inheritance
      • cover interface implementation
      • cover concatenation properties and laws
      • cover parsing consistency and idempotence
      • complete comprehensive coverage validation
      • optimize test organization and clarity
  3. Perform "horizontal attack" using checkpoints
  4. Enforce
    • warn when coverage thresholds are not met

Sub-issues

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions