-
Notifications
You must be signed in to change notification settings - Fork 19
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
Acceptance test time improvement #142
Comments
WIP acceptance test cleanup:
|
…ng acceptance tests with failed steps
… class_refresh_db from some classes that don't alter DB data
1fa9f90 added
|
I've done as much as I reasonably can for this issue; test time is down to ~15-17 minutes. The big win would be speeding up the selenium tests, as they're currently standing up Chrome/selenium, GETing a page, and tearing it down, for every test method that does browser tests. I only see 3 ways to do that, none of which sound terribly good:
|
Issues/142 - Acceptance test time improvements
With #141 and the move from PhantomJS to Chrome, acceptance test runtime has gone up from 17-18 minutes to 19-21 minutes. Look into what we can do to speed up acceptance test runs.
While the pytest
--durations=10
report shows actual tests - usually either data creation or web interaction - taking the longest, there are probably a number of things we can do to try and improve overall performance:reflect()
,drop_all()
andcreate_all()
. See if we can generate raw SQL to do this (empty db, create models, load test data) and if that would be faster.time.sleep()
The text was updated successfully, but these errors were encountered: