Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat (hardware-testing): add JIRA functionality to testing scripts (#…
…16013) <!-- Thanks for taking the time to open a Pull Request (PR)! Please make sure you've read the "Opening Pull Requests" section of our Contributing Guide: https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests GitHub provides robust markdown to format your PR. Links, diagrams, pictures, and videos along with text formatting make it possible to create a rich and informative PR. For more information on GitHub markdown, see: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax To ensure your code is reviewed quickly and thoroughly, please fill out the sections below to the best of your ability! --> # Overview This pull request adds a few new features to existing hardware testing scripts and a small bug fix. ## Test Plan and Hands on Testing I ran every new script on robots while initiating errors and trying to break them. All changes to the jira_tool script work with every current references of the script. ## Changelog First, the speed_accel_profile script can now post results and raw data to Jira and print a summary of the test outside of Jira. Next, in the "gripper_and_zmount_move" you can now change the distance, log results, and post results to a Jira ticket. Both of these script changes required a few small changes and additions to the jira_tool script. Also, both of these scripts can be used without Jira integration and outside of ABR. Lastly, a bug in the abr_robot_error script that prevented LPC data from being collected was fixed. ## Review requests Checking message statements and if some functions should be defined in different scripts. ## Risk assessment Not much, this only affects ABR and hardware testing scripts. <!-- - Indicate the level of attention this PR needs. - Provide context to guide reviewers. - Discuss trade-offs, coupling, and side effects. - Look for the possibility, even if you think it's small, that your change may affect some other part of the system. - For instance, changing return tip behavior may also change the behavior of labware calibration. - How do your unit tests and on hands on testing mitigate this PR's risks and the risk of future regressions? - Especially in high risk PRs, explain how you know your testing is enough. -->
- Loading branch information