Sha256: cae18dc3e5d353949b12c99fa7be3ed424a514f6aa8a68b0dca53d2657bbd837
Contents?: true
Size: 1.1 KB
Versions: 3
Compression:
Stored size: 1.1 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
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
xcpretty-0.0.9 | features/junit_report.feature |
xcpretty-0.0.8 | features/junit_report.feature |
xcpretty-0.0.7 | features/junit_report.feature |