-
Notifications
You must be signed in to change notification settings - Fork 178
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
fix(app): return calibration flow even if pipette is already calibrated #14506
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## chore_release-7.2.0 #14506 +/- ##
=======================================================
- Coverage 67.74% 67.74% -0.01%
=======================================================
Files 2517 2517
Lines 72068 72066 -2
Branches 9278 9278
=======================================================
- Hits 48823 48819 -4
Misses 21027 21027
- Partials 2218 2220 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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!
expect( | ||
getPipetteWizardStepsForProtocol({ left: null, right: null }, [], LEFT) | ||
).toStrictEqual(mockFlowSteps) | ||
}) | ||
it('returns the calibration flow only when correct pipette is attached but there is no pip cal data', () => { | ||
it('returns the calibration flow only when correct pipette is attached even if htere is pip cal data', () => { |
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('returns the calibration flow only when correct pipette is attached even if htere is pip cal data', () => { | |
it('returns the calibration flow only when correct pipette is attached even if there is pip cal data', () => { |
fix RQA-2357
Overview
In setup to run when a pipette is correctly attached and calibrated, we should still open the calibration flow when the user presses "recalibrate"
Test Plan
On ODD, with a pipette attached and calibrated, go to run setup and press "Recalibrate" - the calibration flow should launch as expected
Changelog
getPipetteWizardStepsForProtocol
if a pipette is properly attached, regardless of whether it is already calibratednull
instead of[]
for bothgetPipetteWizardStepsForProtocol
andgetPipetteWizardSteps
to take advantage of null handling in thePipetteWizardFlows
componentReview requests
Look over code - I've already tested this
Risk assessment
Low