This is a tracking bug for the new Lettuce parser I've been working on.
This branch includes:
Where is it at:
Timer on test_xunit_output.py:test_xunit_output_with_no_steps has increased.
It used to be ~0 and now it is ~0.0003 any ideas on speed improvements?
This scenario is the one where there are no steps defined, it kind of makes sense to have a really short fail time.
I agree, but for the moment I'm focused on robustness and stability before I profile the code. This said there's not heaps of difference between 0s and 0.0003s, that doesn't phase me too much. Especially as my focus is on making big files much faster. I do notice though that the unit tests take approximately 20x as long though, so it's possible the setup and teardown time is quite high.
So...resolution would be to change the test slightly (increase fail time)for now and open an issue for it?
I'd blank the timings out from the tests.
I think we should keep the test but increase the time, add a new performance issue.
The pull request is #430