Sha256: 2eac5f0da5ac5321ba7cf1d2495c44e7e50ac76d1e6f3f1099430161d1ab15a9

Contents?: true

Size: 1.46 KB

Versions: 2

Compression:

Stored size: 1.46 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 "junit" report paths
        Then I should have test reports in two custom paths

Version data entries

2 entries across 2 versions & 1 rubygems

Version Path
xcpretty-0.1.4 features/junit_report.feature
xcpretty-0.1.3 features/junit_report.feature