Geek asks and answers

The cucumber test suite is too slow for Travis

I have a cucumber test suite for my rails application that includes about 500 scripts with approximately 5,000 steps between them.

I installed my github repository to use Travis-CI using the following .travis.yml.

language: ruby
rvm:
  - "1.9.2"
script:
  - RAILS_ENV=test bundle exec rake db:migrate --trace
  - bundle exec cucumber -f progress -r features features/cards/base_game
  - bundle exec cucumber -f progress -r features features/cards/basic_cards
  - bundle exec cucumber -f progress -r features features/cards/intrigue
  - bundle exec cucumber -f progress -r features features/cards/seaside
  - bundle exec cucumber -f progress -r features features/cards/prosperity
  - bundle exec cucumber -f progress -r features features/cards/interactions
before_script:
  - cp config/database.travis.yml config/database.yml
  - psql -c 'create database dominion_test' -U postgres

I split the execution of the cucumber when Travis threw out Out Of Memory, if I just ran bundle exec cucumberto run all cases.

However, my last push spawned Travis's task, which took more than 50 minutes to run all my tests, and was therefore killed. Am I just unsubstantiated with this many scenarios, or can I do something to speed things up?

. , , . , .

+5
1

, , Travis.

, (, !) . .travis.yml , 15 , :

language: ruby
rvm:
  - "1.9.2"
env:
  - CARD_SET=base_game
  - CARD_SET=basic_cards
  - CARD_SET=intrigue
  - CARD_SET=seaside
  - CARD_SET=prosperity
  - CARD_SET=interactions
script:
  - RAILS_ENV=test bundle exec rake db:migrate --trace
  - bundle exec cucumber -f progress -r features features/cards/$CARD_SET
before_script:
  - cp config/database.travis.yml config/database.yml
  - psql -c 'create database dominion_test' -U postgres
+5

More articles:


All Articles