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
Faster unit tests by re-using GPG directory #5683
Faster unit tests by re-using GPG directory #5683
Conversation
e1322a8
to
b3b80db
Compare
@nabla-c0d3 Rebasing should fix the safety check failure (resolved via #5686) |
b3b80db
to
c2b7a47
Compare
Codecov Report
@@ Coverage Diff @@
## develop #5683 +/- ##
========================================
Coverage 85.54% 85.54%
========================================
Files 52 52
Lines 3771 3771
Branches 474 474
========================================
Hits 3226 3226
Misses 440 440
Partials 105 105 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest looks good. Thank you @nabla-c0d3 for this. It will surely speedup the tests.
Fix lint Fix types
c2b7a47
to
50853df
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Approved.
Status
Ready.
Description of Changes
This PR fixes #4331 by updating the
config
fixture to have it re-use the same GPG directory across all tests via asession
scope.More specifically, the code that imports the test GPG key within the
config
fixture takes 2s to run on my laptop. This adds a 2s setup call to every single unit test that relies on theconfig
fixture. A lot of tests do use this fixture (directly or indirectly). For example, the first parallel run of app-tests on CircleCI takes 22 minutes to complete for this PR, instead of 28 minutes.However, this PR is more about improving the developer experience when constantly running a few tests locally, while building a feature. Having a 2s delay on each test makes iterating on a feature much slower.