Recommended way of running Cucumber Tests on Teamcity
Hiya!
TeamCity Professional 2017.2.3 (build 51047)
Using this old version as in 2019, there is still a bug preventing "vintage j4 tests running"
I've tried sharing a cucumber configuration (from intelliJ) for teamcity to run, however this is not supported

Ive also tried a junit runner using
@RunWith(Cucumber.class)
which also works locally, however gives me an error on TC
```
[Step 6/6] Running 'CucumberFeatureRunner'
[10:25:37][Running 'CucumberFeatureRunner'] Starting run configuration CucumberFeatureRunner ...
[10:25:37][Running 'CucumberFeatureRunner'] java
[10:25:38][java] Error: Could not find or load main class null
[10:25:38][java] Java returned: 1
```
What is the recommended approach? I've previously had such good experiences with Teamcity, citing to my company it can so easily do anything intelliJ can, but in a automated fashion, however I'm struggling to get my cucumber tests to run.
Please sign in to leave a comment.
Ive tried both with
where my feature files are in tests/e2e/features
And also
where the I have my features in tests/resources/cucumber/features/e2e
These both work running the junit class in intelliJ, but not on teamcity
Hi Mike,
I'm afraid that our IDEA runner does not support cucumber as of now. We have a couple feature requests for it:
https://youtrack.jetbrains.com/issue/TW-30422
https://youtrack.jetbrains.com/issue/TW-22273
They are pretty old but have almost no votes, so we haven't really moved on with implementing them so far. Feel free to vote for them and add any comments you consider appropriate, they have been parked for quite some time so maybe some votes and scenario descriptions would help bring them to the attention of the devs.
In the meantime, you might want to run this tests via maven or any other option that cucumber supports. All other integrations with teamcity (such as test reporting, etc) should still work just fine if using maven, and if you are using the command line you can use the XML Report processing tool for post-build test processing.
Hope this helps.