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
User had to navigate to TC info tab to view TmsLink info
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
As a user I'd like to have 1-click action feature to export all failed/broken/skipped test cases to some readable format representation.
The information in this representation should contain failed/broken sections, TmsLink value, method name(ideally) and fail reason. TestCaseID pattern should support TmsLink pattern, therefore be clickable.
I'm submitting a ...
What is the current behavior?
User had to navigate to TC info tab to view TmsLink info
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
As a user I'd like to have 1-click action feature to export all failed/broken/skipped test cases to some readable format representation.
The information in this representation should contain failed/broken sections, TmsLink value, method name(ideally) and fail reason. TestCaseID pattern should support TmsLink pattern, therefore be clickable.
E.g.
-- TestCaseID-111
--- testCaseMethodName1
---- failureReason1
-- TestCaseID-123
--- testCaseMethodName2
---- failureReason2
-- TestCaseID-222
--- testCaseMethodName3
---- failureReason3
-- TestCaseID-234
--- testCaseMethodName4
---- failureReason4
What is the motivation / use case for changing the behavior?
Better(faster) failed/broken test cases handling
Please tell us about your environment:
Other information
The text was updated successfully, but these errors were encountered: