Progress vs pretty output -- Progress is WAY slower! about behat HOT 4 OPEN

I tested your thesis but cannot confirm this with my test suite ... (well 'my' suite its also a lot faster but still :D)

progress 1:

460 scenarios (460 passed)
12432 steps (12432 passed)
0m31.15s (151.45Mb)

progress 2:

460 scenarios (460 passed)
12432 steps (12432 passed)
0m29.88s (148.31Mb)

pretty:

460 scenarios (460 passed)
12432 steps (12432 passed)
0m30.27s (148.34Mb)

from behat.

No idea why but for us it's notably slower!

I'm more curious how you're getting 460 scenarios to pass in 30s though!

from behat.

Just a few tests for an event-sourced-content-repository called Neos :D

https://github.com/neos/neos-development-collection/tree/9.0/Neos.ContentRepository.BehavioralTests/Tests/Behavior/Features

I didnt write them but they're great and apparently not so slow :D

from behat.

Ah gotcha. We're using Drupal. Notably slower. Trying to add parallelization and that's proving challenging since each scenario creates a user etc etc. Quickly overwhelms SQL and times out.

from behat.