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

Add an ability to export failure results #405

Closed
1 task done
AlexanderPoleschuk opened this issue Jun 14, 2017 · 2 comments
Closed
1 task done

Add an ability to export failure results #405

AlexanderPoleschuk opened this issue Jun 14, 2017 · 2 comments
Labels
type:new feature Change that add something new for end users

Comments

@AlexanderPoleschuk
Copy link

AlexanderPoleschuk commented Jun 14, 2017

I'm submitting a ...

  • feature request

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.

  • Failed test cases

-- TestCaseID-111
--- testCaseMethodName1
---- failureReason1
-- TestCaseID-123
--- testCaseMethodName2
---- failureReason2

  • Broken test cases

-- 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:

  • Allure version: 2.1.1
  • Test framework: testng@6.10
  • Allure adaptor: allure-testng@2.0-BETA8

Other information

@baev baev added the type:new feature Change that add something new for end users label Jun 14, 2017
@baev
Copy link
Member

baev commented Jun 14, 2017

related to #273

@baev
Copy link
Member

baev commented Jun 14, 2017

should be fixed via #273

@baev baev closed this as completed Jun 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:new feature Change that add something new for end users
Projects
None yet
Development

No branches or pull requests

2 participants