Badges awarded by OVP 2.0 program rely on automated testing against predefined requirements. Each badge relates to a specific set of requirements and tests that must be passed in order for the badge to be awarded. The tests and requirements come from various Open Source communities. In order for OVP 2.0 to be able to award a badge, the following criteria must be met for these requirements and tests.
- Requirements are uniquely identifiable and published as a permanent, immutable reference as part of a project release (i.e. Each badge can point to a set of point-in-time requirements that will not change)
- Testing tools/libraries are published as versioned artifact(s).
- Documentation of how to execute the tests are published with and pinned to the versioned artifact released
- Mapping of tests to requirements are provided (can be from either the testing project or requirement project).
- For example: For CNTT-related badges this mapping will be provided by the RC-2
- Test tools can produce a result format compatible with OVP 2.0
- This can be achieved by the test tool directly creating the result package or a supplemental script converting to the target format
- Link to reference OVP input format (DRAFT)