-
Notifications
You must be signed in to change notification settings - Fork 455
CDRIVER-3422 add unified test setup/teardown #699
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
test_runner_t *test_runner; | ||
test_file_t *test_file; | ||
test_t *test; | ||
} test_diagnostics; |
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 yet clear to me whether this is useful. The spec recommends not aborting while a test is running so server state can be cleaned up:
If at any point while executing this test an unexpected error is encountered or an assertion fails, the test runner MUST consider this test to have failed and SHOULD continue with the instructions in this section to ensure that the test environment is cleaned up (e.g. disable fail points, kill sessions) while also forgoing any additional assertions.
I plan to havetest_run
return an error instead of aborting when something within the test fails. So, if that means the signal handler diagnostics is not useful, I may remove it later.
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.
LGTM!
Tweak make_release.py - add requirements.txt for dependencies - add --skip-distcheck option - fail if running on Python 2 - fix some pylint errors - refactor running shell script
This is part 2 of unified test runner:
Next up: creating and tearing down the entity map for each test.