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

Issue-464: proper handling of abort and slight improved KarateJunitFormatter #465

Closed
wants to merge 1 commit into from

Conversation

vmchukky
Copy link
Contributor

Description

As discussed with @ptrthomas (#464), this PR is to

  • let karate.abort() also mark the remaining steps in that scenario as SKIPPED (same as the steps after failed step of a scenario)

  • slightly improve KarateJunitFormatter (invoke updateElement in endOfScenarioLifeCycle)

  • make sure the above changes still won't impact KarateJunitAndJsonReporter; it will report aborted scenario as passed (as it is doing in 0.8.0), please see newly added test case (FeatureResultTest.java)

  • make sure KarateHtmlReporter can identify skipped steps (after abort() or failure) of a scenario are marked properly

  • Relevant Issues : Issues with skipped tests in summary and html report #464

  • Relevant PRs : (optional)

  • Type of change :

    • New feature
    • Bug fix for existing feature
    • Code quality improvement
    • Addition or Improvement of tests
    • Addition or Improvement of documentation

@vmchukky
Copy link
Contributor Author

sorry, I just realized it was raised against master instead of develop, closing it (will open a new one)

@vmchukky vmchukky closed this Jul 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant