-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add "unwanted coverage" to user documentation #431
Comments
There are no hard-coded artifact types in OFT. That is part of the acknowledgement that "one-size-fits-all" does not really work in all projects. "Unwanted coverage" means that the specification item (in this case a code tag) claims to cover something, but the thing it points to does not exist. That happens usually when there is a typo in the requirement ID. But you are right, the handbook should definitely explain what "unwanted coverage" means. |
I have a simple project setup.
Now, I get
As beginner user, I expect that https://github.com/itsallcode/openfasttrace/blob/main/doc/user_guide.md days something about the case.
Are the artifact types at https://github.com/itsallcode/openfasttrace/blob/main/doc/user_guide.md#specification-item-id hard-coded in the system?
It seems that they are hard-coded in the system. Then, the following sentence needs to be rewritten:
Maybe at https://github.com/itsallcode/openfasttrace/blob/main/doc/user_guide.md#writing-a-specification?
The solution to my concrete case is to add following to the requirement:
The text was updated successfully, but these errors were encountered: