Describe the story
Provide a clear description of the new feature or improvement to existing functionality.
Logging statements should not be overly asserted in unit tests. This makes unit tests more brittle. However, there are scenarios where logging statements should be asserted; primarily when the logging output is critical to debugging or functionality.
Add the following statement to the Copilot instructions:
- Do not assert logging output unless critical to functionality.
Update the unit tests to remove logging assertions.
Acceptance criteria
Provide clear acceptance criteria to validate the story is complete.
Gherkin syntax example:
Given the 'PERSONA' has 'DONE SOMETHING'
When the 'PERSONA' does 'ONE THING'
Then the 'PERSONA' must do 'ANOTHER THING'
Additional context
Add any other context about the story here.
Describe the story
Provide a clear description of the new feature or improvement to existing functionality.
Logging statements should not be overly asserted in unit tests. This makes unit tests more brittle. However, there are scenarios where logging statements should be asserted; primarily when the logging output is critical to debugging or functionality.
Add the following statement to the Copilot instructions:
Update the unit tests to remove logging assertions.
Acceptance criteria
Provide clear acceptance criteria to validate the story is complete.
Gherkin syntax example:
Additional context
Add any other context about the story here.