Skip to content

docs: Add parser testing strategy discussion paper#132

Open
Bernadette-Mohr wants to merge 1 commit intodevelopfrom
parser_testing_strategy
Open

docs: Add parser testing strategy discussion paper#132
Bernadette-Mohr wants to merge 1 commit intodevelopfrom
parser_testing_strategy

Conversation

@Bernadette-Mohr
Copy link
Copy Markdown
Collaborator

  • Covers unit, integration, and E2E testing principles
  • Includes examples and best practices
  • Documents testing schedule and anti-patterns

Copy link
Copy Markdown
Collaborator

@ndaelman-hu ndaelman-hu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I already provided most of my feedback yesterday. I think the intro is new, so I just checked that.


* For any function with conditional logic (if/else, loops)
* For data transformation functions (parsing, formatting, validation)
* For calculations and algorithms
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is kind vague

* **Document behavior**: Unit tests serve as executable documentation of what each function should do
* **Catch logic errors: Off-by-one errors, incorrect conditionals, edge cases in algorithms**

#### When to write
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would redo this section, as it is kinda hand-wavy. More important is that tests build of off expected formats or interfaces (enhanced with type hinting). Lastly, don't forget that Coveralls already provides metrics for how well our tests cover the repo.

@ndaelman-hu
Copy link
Copy Markdown
Collaborator

I suggest that we start focusing on applying the framework.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants