Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speed up tests #71

Closed
pcolby opened this issue Aug 22, 2016 · 2 comments
Closed

Speed up tests #71

pcolby opened this issue Aug 22, 2016 · 2 comments

Comments

@pcolby
Copy link
Owner

pcolby commented Aug 22, 2016

It now takes 3 hours for Travis CI and just over 6 hours on AppVeyor, to run through all tests on all configurations.

Anything we can do to reduce this will bring compound time savings.

@pcolby
Copy link
Owner Author

pcolby commented Aug 22, 2016

I think we can speed up the tests quite significantly if we maintain a dictionary of (read-only) parsed sessions instead of re-parsing each session for each test type. Specifically, parsing the session samples data is quite time-consuming.

pcolby added a commit that referenced this issue Aug 23, 2016
Specifically, our custom recursive fuzzy XML compare routines were not
aborting on the first failure, as QVERIFY / QCOMPARE and friends do.

This change should also mean that small, repeated errors, like the
recent locale and rounding errors, finish much sooner on CI platforms
like Travis CI and Appveyor, and now longer bring down their Web UIs!
pcolby added a commit that referenced this issue Aug 23, 2016
This cuts the total time of full unit test runs down to about one third
of what it was (eg from ~12 minutes down to ~4 minutes). That's a
pretty huge saving! :D (wish I'd thought of it earlier!)
pcolby added a commit that referenced this issue Aug 23, 2016
This should fix a bug introduced in commit f8394e9 (#71).
@pcolby
Copy link
Owner Author

pcolby commented Aug 23, 2016

Well that's got it down to half... so pretty good improvement for now 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant