The project MUST use at least one automated test suite that is publicly released as FLOSS. It MUST clearly show or document how to run the test suite(s). A test suite SHOULD use a standard testing framework and be invocable in a standard way for that language. It is SUGGESTED that the test suite cover most (or ideally all) the execution paths, input fields, and functionality.
Notes:
A test suite contains the code (test-code) that tests the actual project code and should use a test framework to execute the test-code.
The test suite may be maintained as a separate FLOSS project.
Fulfillment Examples:
A Python project using PyTest as test framework to create the test suite and has instructions on how to run the tests in a typicall file like BUILD.md, README.md, or CONTRIBUTING.md.
A Java project having all testing code (JUnit) included and executed automatically as part of the CI pipeline, e.g., on pull requests to the main branch, or manually on the local machine for validation of changes.
20. Testing Practices
The project MUST use at least one automated test suite that is publicly released as FLOSS. It MUST clearly show or document how to run the test suite(s). A test suite SHOULD use a standard testing framework and be invocable in a standard way for that language. It is SUGGESTED that the test suite cover most (or ideally all) the execution paths, input fields, and functionality.
Notes:
Fulfillment Examples:
BUILD.md,README.md, orCONTRIBUTING.md.