Sebastian Bär
Sebastian Bär
The following two requirements were removed ahead of the OFT API design: # From the spec #### Plain Text Report Options `req~reporting.plain-text.report-options~1` The following parts of the plain text reports...
# Situation Integration test should be runnable in a separate test phase. The fail save plug-in established the standard naming convention for integration tests: https://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#includes # Acceptance Criteria 1. Integration...
As a user I want OFT to only import new or changed artifacts for my project in order to speed up the import process. ## Acceptance Criteria 1. OFT remembers...
As a user I want OFT to run on all processor cores of my machine in order to get requirement coverage feedback as fast as possible. ## Acceptance criteria 1....
## Situation The plain text report is mainly used to debug problems in the tracing chain. It needs to be compact. But it also needs to be as readable as...
## Thank you very much for contributing to the development of our product! ### Before creating a pull request, we want to make sure that you're aware of some constraints:...
## Situation When a server answers with HTTP status code 301 (redirect permanent) the link checker treats this as a broken link, even if the link the redirect points to...
## Situation For data exchange we currently support the machine readable "SpecObject" and "ASPEC" formats. While these are technically sufficient, they show their heritage over three predecessor tools (TReqs, ReqM2...