Skip to content

Conversation

yeshwant-singh-zz
Copy link

Summary

Adding status in junit xml report for individual test cases.

Details

In junit xml report generator, individual testcase/scenario status is not shown.

Motivation and Context

  • I wanted to send html report of cucumber tests , for that I was creating a simple table like html in which individual testcases's status, time are shown in rows. Time was mentioned in xml report for each scenario/testcase, but status was not mentioned.
  • I tried to write an XSLT file reading the xml file and added conditions like if std error is mentioned then scenario is passed else failed.
  • But finally I added this change in junit file and made my work easy.

How Has This Been Tested?

  • Ran the tests for failed and passed scenario each.
  • Test setup: ruby 2.3, cucumber 2.4.0
  • Code doesn't effect any other areas

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I've added tests for my code
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@yeshwant-singh-zz
Copy link
Author

fixed test cases

@yeshwant-singh-zz
Copy link
Author

Fixed all the test cases , build passing

@stale
Copy link

stale bot commented Nov 8, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the ⌛ stale Will soon be closed by stalebot unless there is activity label Nov 8, 2017
@stale
Copy link

stale bot commented Nov 15, 2017

This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective.

@stale stale bot closed this Nov 15, 2017
@lock
Copy link

lock bot commented Nov 15, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

⌛ stale Will soon be closed by stalebot unless there is activity

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants