-
Notifications
You must be signed in to change notification settings - Fork 151
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
Quick Assess HTML report groups requirements incorrectly #6994
Comments
@madalynrose, I ma interested in this repo, please assign this to me. |
Hello there! I'm interested in working on this issue. Could you please assign it to me? |
@thesharifi we've assigned the bug to you. If you're no longer interested, let us know and we'll assign it to the other user who showed interest. |
Implementation note: Please don't change the report package in any way, since it's used by other packages that we create. The optimal path forward may be to leverage the code from |
@thesharifi, any update on this? We might want to assign to someone else if it's not going to happen anytime soon |
@shanmukhasaisai, are you still interested in working on this? The first person to volunteer seems to have lost interest |
Yes, iam interested to work |
@shanmukhasaisai, Sorry for the delay in getting back to you. If you're still available, please take this and run with it. Thanks! |
Describe the bug
The generated HTML report for Quick Assess currently uses the same summary model as Assessment. The assessment summary model groups requirements by Assessment. This means that the test details here display the Assessment title, not requirement titles. It also means that if any requirements are part of the same Assessment, they appear together and that the order of requirements is not respected in this list.
Expected behavior
Test details list requirements by name and show one requirement per title. It should instead use the Quick Assess summary model, as used on the Overview page for Quick Assess.
Screenshots
Are you willing to submit a PR?
Yes
Did you search for similar existing issues?
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: