forked from xcpretty/xcpretty
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathjunit_report.feature
44 lines (35 loc) · 1.66 KB
/
junit_report.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
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 pending test output
Given I have a pending test in my suite
When I pipe to xcpretty with "--report junit"
Then I should see a pending test node in my report
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