Skip to content
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

treat source data for risk table and coverage matrix as a single data set #193

Open
mariev opened this issue Aug 27, 2021 · 0 comments
Open
Labels
future work nice to have change, work on this later

Comments

@mariev
Copy link
Collaborator

mariev commented Aug 27, 2021

risk table pulls from requirements while coverage matrix pulls from test case files without checking other source.

Use req ids (either explicit or dyn. num.) to link these data for completeness and consistency. Of interest:

  1. ordering of reqs/tcs for use with dynamic numbering s/b same
    • regardless of which table is displayed first in report
    • if each table is generated as standalone i.e. requirement report should not have diff numbering than final validation report.
  2. same requirement names for both tables
@mariev mariev added the future work nice to have change, work on this later label Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future work nice to have change, work on this later
Projects
None yet
Development

No branches or pull requests

1 participant