Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

codecept cucumber and testrail test cases #24

Closed
JonP-xpb opened this issue Aug 18, 2020 · 5 comments · Fixed by #37
Closed

codecept cucumber and testrail test cases #24

JonP-xpb opened this issue Aug 18, 2020 · 5 comments · Fixed by #37

Comments

@JonP-xpb
Copy link

I have my scenarios defined in feature files, how can I get the test cases id @cxxxx into the test description?

example of a feature/scenario


Scenario Outline: Get the statistics
Given...
When ...
Then..
Scenarios:
| param a | param b | testrailid |
| xa | xb | @C77444 |
| xc | xd | @C77445 |


how can I include the testrail id in the test object so that its result gets mapped to a testrail test case?
I thought the above might work as each test 'description' includes the scenario table row values
but I am getting "There is no TC, hence no test run is created"

@kobenguyent
Copy link
Owner

Could you provide a sample repo that uses codeceptjs gherkin? I don't use it on daily basis so better to have a ready repo so that I could take a look.

@kobenguyent
Copy link
Owner

Hey @JonP-xpb did you have chance to try the gherkin tag here https://codecept.io/bdd/#advanced-gherkin

@EgorBodnar
Copy link
Contributor

EgorBodnar commented Jul 28, 2021

@JonP-xpb hey!
Your Scenario Outlines must look like:

Scenario Outline: Fill some field
    When I fill some field by text <text>
    Then I see text <text>
    
    Examples:
      | testRailTag | text      |
      | @C123       | someText1 |
      | @C1234      | someText2 |

@EgorBodnar
Copy link
Contributor

@peterngtr it is a temporal solution. Maybe we should add support for this feature?

@EgorBodnar
Copy link
Contributor

@peterngtr the problem is resolved in the PR
I guess the issue should be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants