-
Notifications
You must be signed in to change notification settings - Fork 227
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(allure-karate): fix duplicate scenarios when call or callonce key…
- Loading branch information
1 parent
547c624
commit af64da0
Showing
3 changed files
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 13 additions & 0 deletions
13
allure-karate/src/test/resources/testdata/call-callonce.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
Feature: Call & Call once Feature | ||
This feature calls another feature and demonstrates Allure reporting issue. | ||
|
||
@smoke | ||
Scenario: Main Scenario with a call | ||
Given url 'https://jsonplaceholder.typicode.com' | ||
When method GET | ||
Then status 200 | ||
|
||
* call read('classpath:testdata/apiResponse.feature') | ||
* callonce read('classpath:testdata/api.feature') | ||
|
||
Then print 'Main scenario completed.' |