-
Notifications
You must be signed in to change notification settings - Fork 3
Test infrastructure definiton #61
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
Szelethus
left a comment
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.
Can we move setup_logging here as well?
|
We are learning by trial; this patch is not ready yet. |
8bb540d to
2794f4f
Compare
This is necessary to let other packages in this folder use the common library
45d1c13 to
217dc53
Compare
Szelethus
left a comment
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 took a while, thank you so much for the patience! LGTM! I'm sure we'll find some issues later down the line as we put this base class to the test (haha), but lets move on now.
Szelethus
left a comment
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.
Lets send it.
Why: We have no rigid guidelines or utilities for our testing needs. What: - Created a README.md detailing how to run and extend our test suite. - Created a common library to provide utility for new tests. - The common lib contains the TestBase class with a few modifications: - The check_command has been renamed to run_command; it no longer asserts anything, it returns the exit code, and the stdout and stderr in a tuple - The global variables for the BAZEL_BIN_DIR and BAZEL_TESTLOGS_DIR have been moved into the class as data. They must be set by the test class. - A new variable \_\_test_path\_\_ have been introduced; this is necessary so execution always happens in the specific tests directory. - Added a template test, so new tests can be started with just a `cp -r template/ new_test/` Addresses: Ericsson#22
Why:
We have no rigid guidelines or utilities for our testing needs.
What:
cp -r template/ new_test/Addresses:
#22