Skip to content

Document testing approach #19

@jpmckinney

Description

@jpmckinney

Since the output is expected to change regularly, we can document an approach of:

  1. Generate the original output
  2. Copy to a new location
  3. Make code changes
  4. Generate the new output
  5. Diff

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions