Cucumber: Very slow when run via TeamCity

Hi All,

We recently switched from CruiseControl to TeamCity.  I'm very pleased about the change =)

One issue we are fighting currently is the amount of time it takes for our Cucumber features to run - 1+ hours.  When I navigate to the latest build directory on our build server and run the test via the same rake command that TC would be using they take 4 minutes.  The only noticeable difference I can see is that when TC runs the suite it adds: --format Teamcity::Cucumber::Formatter --expand  to the rake command.  

Has anyone else encountered such an issue?  

One other smaller issue is that pending steps are marked as failures by TC when they should really just be ignored.

Cheers,
DJ

1 comment

Hi All,

We recently switched from CruiseControl to TeamCity.  I'm very pleased about the change =)

One issue we are fighting currently is the amount of time it takes for our Cucumber features to run - 1+ hours.  When I navigate to the latest build directory on our build server and run the test via the same rake command that TC would be using they take 4 minutes.  The only noticeable difference I can see is that when TC runs the suite it adds: --format Teamcity::Cucumber::Formatter --expand  to the rake command.  

Has anyone else encountered such an issue?      

Could you open build results full log and check which activity takes such a long time. Our Cucumber reporter just uses cucumber API and marks stdout, difference shouldn't be such noticeable. Other way is to disable "Cucumber Reporter" in build configuration settings and compare elapsed time according build log. How many features/steps do you have?

0

Please sign in to leave a comment.