When the cuke-tree IDE executes a test run, in order to display a progress bar it first executes a dry run so it can count the number scenarios and so can judge progress. When cuke-tree executes this dry run, it display's cucumber's progress output. When executing a large test suite, this can result in hundreds of lines of output being sent to the console in only a few seconds, which slows down the process. The stdout from cucumber should be suppressed during this dry-run, to speed things up.
When the cuke-tree IDE executes a test run, in order to display a progress bar it first executes a dry run so it can count the number scenarios and so can judge progress. When cuke-tree executes this dry run, it display's cucumber's progress output. When executing a large test suite, this can result in hundreds of lines of output being sent to the console in only a few seconds, which slows down the process. The stdout from cucumber should be suppressed during this dry-run, to speed things up.