-
Notifications
You must be signed in to change notification settings - Fork 4
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
Stanford830 #226
Stanford830 #226
Conversation
…and increasing robustness.
…ow passing the test cases. A debug setting is included to debug the test_driver() function; however, this will bypass the test log. An updated error message is included to point to setting the debug parameter to true for debugging purposes.
…uitive debugging. Now only logs tests when they pass. Note: The Stanford830 driver has a buffer_points attribute mentioned in the docstring but nowhere else and so is failing the test nb. Make sure this is fixed in the stanford830 branch.
…utes and methods have corresponding doc strings, but that all attributes and methods listed in the docstring are implemented in the drivers contents. Needs to be tested.
…e readable line breaks. Must be tested.
…s now have a verbose option (defaults to True), to offer an option to clean up outputs which have been further refined in general. Testing for implementation and presence of attributes and methods in drivers docstrings is now implemented and validated. Furthermore, since we are now only logging the most recent passing of drivers, test logging has been updated to only save one line for simplicity, legibility, and maintainability, unless otherwise specified through the save_multiple_lines parameter.
Please note, the readthedocs build initially failed, and then succeeded once I entered an empty commit with absolutely no changes to it. Nothing to take action with but something to be aware of. |
Also, the stanford830 is not passing test cases because it has buffer_points in the docstring but not in the driver itself. This should be fixed before this PR is pulled. |
… logging results.
…to stanford830
…pends on time constant
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.
tested with Stanford830 on bench and looks good.
The test_driver() function has been updated to include a debugging option. The stanford830 has been updated to follow proper docstring syntax. The test cases are passing and this is reflected in the test log.