Documentation for usage with multiple test suites run in parallel

[streetlogics]

Mentioned here - https://github.com/codeclimate/ruby-test-reporter/issues/134#issuecomment-330916664, it seems that when one is using two different test suites and parallelizing those tests that configuring things gets a bit tricky. I played around with a few different circleci configs trying to get it working (using this as a starting point https://docs.codeclimate.com/docs/circle-ci-test-coverage-example), but it kept wanting to run every test instead of a subset of the tests for that specific container being parallelized. Do you guys have an example for getting this working where the existing circle test section looks like this for parallelization and distributing tests evenly according to the time it takes to run them:

test:
  override:
    - mkdir -p $CIRCLE_TEST_REPORTS/cucumber:
        parallel: true
    -  PRECOMPILE=true bundle exec cucumber --format json --out $CIRCLE_TEST_REPORTS/cucumber/tests.cucumber:
        parallel: true
        files:
          - features/*.feature
    - bundle exec rspec --format doc --format RspecJunitFormatter --out $CIRCLE_TEST_REPORTS/rspec.xml:
        parallel: true
        files:
          - spec/**/*_spec.rb

[davehenton]

Hey @streetlogics. You can find more info on configuring the reporter with multiple test suites in our docs here. If you still have questions afterwards, ping us over at support, and include the following info:

• Name of your repo
• A copy of your CI configuration file
• Output from your CI (after including the --debug flag in your CI configuration)
• A copy of your codeclimate.json (this can be generated inside your coverage folder by running ./cc-test-reporter format-coverage)
• Any relevant screenshots of your setup

Looking forward to getting you up and running!

[ale7714]

👋 @streetlogics, sorry for the late follow up on this. We recently added an example using Circle CI 2.0 and multiple suites.

Let us know if you have any questions.