eclipse-score / eclipse-score/docs-as-code
Improvement: Add test properties to all tests
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 23h 52m
- Merged PRs (30d)
- 52
Description
Once #220 is merged we can start adding test propterties to all of our tests in order to ensure test coverage & enable statistics.
This uses the decorator introduced in latest tooling commits. See [here](https://github.com/eclipse-score/tooling/tree/main/python_basics/score_pytest#using-the-test-properties-plugin)
There is still outstanding issues regarding how to understand the different Test-Types & Derivation Techniques.
Relevant Process =>
- [here](https://eclipse-score.github.io/process_description/main/process_areas/verification/verification_concept.html#verification-concept-types-methods)
- [here](https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_specification.html)
- [here](https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_process_toolreqs.html)
----
Edit:
As we currently do not understand the way to use this.
So we are not blocked until this is clarified we will use the following attributes (test_type & derivation_technique) for all tests and adapt them once this is better understood
```
@add_test_properties(
partially_verifies=["", ""],
test_type="requirements-based",
derivation_technique="requirements-analysis",
)
````
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.