Sha256: d76415564b7eca3232e615ddca00b6f2d3309b4d941bfee57a9fb1e486f6e4e0
Contents?: true
Size: 1.45 KB
Versions: 3
Compression:
Stored size: 1.45 KB
Contents
Feature: Creating a JUnit test report Background: Given the tests have started running Scenario: Showing a test suite Given I have a passing test in my suite When I pipe to xcpretty with "--report junit" Then I should see a test suite node Scenario: Showing failed tests Given I have a failing test in my suite When I pipe to xcpretty with "--report junit" Then I should see a failed test node in my report Scenario: Showing passing tests Given I have a passing test in my suite When I pipe to xcpretty with "--report junit" Then I should see a passing test node in my report Scenario: Counting tests Given I have a passing test in my suite And I have a failing test in my suite And the test suite has finished When I pipe to xcpretty with "--report junit" Then I should see 2 tests in my report Scenario: Having many test classes Given I have tests in my suite from 2 classes When I pipe to xcpretty with "--report junit" Then I should see 2 test suites Scenario: Writing to a custom file path When I pipe to xcpretty with "--report junit" and specify a custom path Then I should have a test report in a custom path Scenario: Writing to multiple custom file paths When I pipe to xcpretty with two custom report paths Then I should have test reports in two custom paths
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
xcpretty-0.1.2 | features/junit_report.feature |
xcpretty-0.1.1 | features/junit_report.feature |
xcpretty-0.1.0 | features/junit_report.feature |