I just upgraded a test suite to the latest Codeception 2.1.5, and found many of the acceptance tests (using WebDriver and PhantomJS 1.9.8) now run and blazingly slow speeds... several tens of seconds for single checks, and several minutes for whole test cases.
That's no criticism of Codeception - the html pages of the app are pretty poorly structured, and the the tests are fairly brute force to begin with, but I'm wondering if there is any way to get more specific detail on what is causing the bottleneck. I know to use --debug and --verbose, and that shows that tests often seem to be hanging upon statements that set options, fill text areas, or otherwise use XPath or CSS selectors.
Does anyone have any other suggestions for an approach to the situation to get an idea of what might be going on behind that interface?
(davert - codeception is a great contribution, thanks!)