Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Testing policy #895

Closed
3 tasks done
Tracked by #886
ianlewis opened this issue Sep 22, 2022 · 1 comment
Closed
3 tasks done
Tracked by #886

[docs] Testing policy #895

ianlewis opened this issue Sep 22, 2022 · 1 comment
Labels
type:documentation Improvements or additions to documentation

Comments

@ianlewis
Copy link
Member

ianlewis commented Sep 22, 2022

From OpenSSF best practices:

  1. The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite. [test_policy] - See CONTRIBUTING.md
  2. The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project. [tests_are_added] - Maybe we need contributor docs on code coverage requirements?
  3. It is SUGGESTED that this policy on adding tests (see test_policy) be documented in the instructions for change proposals. [tests_documented_added] - See CONTRIBUTING.md
@ianlewis ianlewis added the type:documentation Improvements or additions to documentation label Sep 22, 2022
@ianlewis
Copy link
Member Author

The criteria here is met by CONTRIBUTING.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant