Part of #6393.
Problem
The Testing section of CONTRIBUTING.md is currently a single, aspirational sentence ("Testing is a key component in the development workflow.") with no actual guidance or requirement. doc/Developing.md explains how to run the unit tests but never states that contributions are expected to add or update tests.
Proposed change
Replace the stub Testing section in CONTRIBUTING.md with explicit guidance that:
- Fixes and features are expected to add or extend automated tests in the
AppInstallerCLITests project (and E2E tests in AppInstallerCLIE2ETests where relevant).
- Describes at a high level how to build and run the tests, linking to
doc/Developing.md ("Running Unit Tests").
- Notes that PRs without appropriate test coverage may be asked to add it before review completes.
Notes for engineers
Please confirm the exact bar we want to set: unit vs. E2E expectations, when tests can be reasonably omitted (e.g., pure doc changes), and any coverage guidance.
Acceptance criteria
CONTRIBUTING.md Testing section states the expectation to add/update tests and links to how to run them.
(Created with GitHub Copilot assistance.)
Part of #6393.
Problem
The Testing section of
CONTRIBUTING.mdis currently a single, aspirational sentence ("Testing is a key component in the development workflow.") with no actual guidance or requirement.doc/Developing.mdexplains how to run the unit tests but never states that contributions are expected to add or update tests.Proposed change
Replace the stub Testing section in
CONTRIBUTING.mdwith explicit guidance that:AppInstallerCLITestsproject (and E2E tests inAppInstallerCLIE2ETestswhere relevant).doc/Developing.md("Running Unit Tests").Notes for engineers
Please confirm the exact bar we want to set: unit vs. E2E expectations, when tests can be reasonably omitted (e.g., pure doc changes), and any coverage guidance.
Acceptance criteria
CONTRIBUTING.mdTesting section states the expectation to add/update tests and links to how to run them.(Created with GitHub Copilot assistance.)