You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What build(s) the test was run for. (How do we determine all the interconnected pieces?)
The names of all the services we are running against
A relationship between features and all test cases run.
Collapsable list of all features. Each set of tests for the future underneath.
Test show pass/fail/blocked. These should NOT roll up to the feature level.
Collapsible list of cucumber steps with results for each step.
Expand/collapse all buttons.
Screenshots/videos are embedded as thumbnails and can be clicked to get bigger.
If a test fails, there needs to be a reason box that allows us to submit a reason for why we are shipping something with failed tests. Regulatory requirements require us to do this at the feature level.
(Look into access control using SSO)
Approval - Export as a PDF to be put in an approval system.
The text was updated successfully, but these errors were encountered:
MVP:
The text was updated successfully, but these errors were encountered: