test(labware-library): mock file-saver while using cypress #5932
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
overview
Addresses LC side of #5457. If we like this approach, I'll repeat it for PD's use of
file-saver
to close that issueNote: I think we have a ticket somewhere for not having mu's in the filenames, but I didn't want to address that in this PR, too separate of a concern to fit in here. Plus now that we have a test for the file name, we can TDD that when we get to it 🙃
changelog
review requests
make -C labware-library dev
), you should be able to save labware files in LC normallymake -C labware-library test-e2e
make -C labware-library dev CYPRESS=1
then when that's running, in another tab,cd labware-library; yarn cypress open
risk assessment
Low, if it goes really wrong this would block file download in LC, but should be easy to prove that this is still working or not (eg try to d/l in sandbox)