-
Notifications
You must be signed in to change notification settings - Fork 294
Some test refactoring #357
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
Conversation
aaronliu0130
commented
Apr 5, 2025
- increase default pytest timeout to 481s for debugging room
- remove duplicate boost sample for testing inspect headers
- use pytest parametrized instead of parameterized & google todo credit
- add script to update CLI test definitions
Sometimes, one hath th'need to debugst the tests. And 60s turned the good ol' debugger into Indiana Jones escapingst a rolling boulder. No more.
Before this, the exclude test did not test excluding at all and just duplicated all the errors contained in the other two .def's
This unfortunately means we must use test names like test_samples[silly-includeorder_cfirst] now. todo(unknown)s were replaced with the appropriate todo(google)s credit (we do not have the knowledge to be more specific than that)
Obviously, we should still check all the changes to the test definitions. This script just makes finding these changes easier.
@@ -209,4 +208,4 @@ addopts = "--color=yes --cov-fail-under=90 --cov=cpplint" | |||
python_files = [ "*test.py" ] | |||
required_plugins = [ "pytest-cov", "pytest-timeout" ] | |||
testpaths = [ "." ] | |||
timeout = 60 | |||
timeout = 481 |
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.
This seems like a massive change. Is there a particular versions of Python and/or operating system that is so slow?
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.
It's not that it's slow, it's that I oftentimes find myself having to debug the tests, for which 1 minute is not enough for. My average debugging time is about 5 minutes, and 418 is my favorite number.
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.