Cutting end-to-end integration tests from 10m -> 3m #106
threepwave
started this conversation in
Show and tell
Replies: 2 comments 1 reply
-
I've created a new convention to manage this. I'm sure there's a better way so looking for feedback. There are now three conftest files in /tests/ for different configurations:
You could imagine adding conftest_settling.py which would just load settling-specific contracts. This is not perfect because we need to remember to copy conftset_all back to conftest.py before deploying AND all test files need to be updated whenever we update conftest.py but... it works for now. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Based on @ponderingdemocritus's suggestion, I took a chainsaw to the conftest.py to cut out any contracts not relevant to what I'm testing.
It typically takes about 8 minutes for the full test suite to run and get me a simple compile error like "you said crypts instead of crypt in your function call." After this change, the full test suite runs in 176s (about 3 minutes).
Here are the changes I made:
1
)Here's the resulting conftest.py that is configured for Crypts and Caverns development:
Beta Was this translation helpful? Give feedback.
All reactions