Skip to content
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

Merged
merged 4 commits into from
Feb 15, 2024

Conversation

smb2268
Copy link
Contributor

@smb2268 smb2268 commented Feb 15, 2024

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

  1. Return calibration steps from getPipetteWizardStepsForProtocol if a pipette is properly attached, regardless of whether it is already calibrated
  2. Return null instead of [] for both getPipetteWizardStepsForProtocol and getPipetteWizardSteps to take advantage of null handling in the PipetteWizardFlows component

Review requests

Look over code - I've already tested this

Risk assessment

Low

@smb2268 smb2268 requested a review from a team as a code owner February 15, 2024 21:01
@smb2268 smb2268 requested review from mjhuff and removed request for a team February 15, 2024 21:01
@smb2268 smb2268 self-assigned this Feb 15, 2024
Copy link

codecov bot commented Feb 15, 2024

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (9dc8f2d) 67.74% compared to head (1e63a10) 67.74%.

Additional details and impacted files

Impacted file tree graph

@@                   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     
Flag Coverage Δ
app 64.54% <50.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
...tteWizardFlows/getPipetteWizardStepsForProtocol.ts 100.00% <100.00%> (ø)
...anisms/PipetteWizardFlows/getPipetteWizardSteps.ts 86.66% <0.00%> (ø)
app/src/organisms/PipetteWizardFlows/index.tsx 40.00% <33.33%> (-1.74%) ⬇️

Copy link
Contributor

@mjhuff mjhuff left a 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', () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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', () => {

@smb2268 smb2268 merged commit 9224b13 into chore_release-7.2.0 Feb 15, 2024
21 of 22 checks passed
@smb2268 smb2268 deleted the app_run-setup-recalibrate branch February 15, 2024 21:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants