chore (v7 vr-tests): Completely remove usage of Screener#26049
chore (v7 vr-tests): Completely remove usage of Screener#26049TristanWatanabe merged 9 commits intomicrosoft:7.0from
Conversation
msft-fluent-ui-bot
left a comment
There was a problem hiding this comment.
It looks like this change to the 7.0 branch may not have been submitted to master yet. Now that version 8 has released, all changes must be submitted to the master branch first (except in emergencies or if the change is irrelevant to version 8).
Please do one of the following:
- If you've already created a PR to
master, add a link to it - If the change is irrelevant to version 8, add a comment explaining why
- Otherwise, create a PR to
masterwith this same change, and add a link to it
After that, you can dismiss this review and remove the "needs cherry-pick" label (or ask a team member to help do so).
Want to avoid this in the future? Include text like "Cherry-pick of ####" in the PR description (where #### is the real master PR number).
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 35a4339:
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: f5a186ae8f17bc97aae19de9403ca15350bc1cab (build) |
🕵 FluentUI-v7 No visual regressions between this PR and main |
Perf AnalysisNo significant results to display. All results
|
Changes:
Screenerspecific configs and scripts from vr-tests package and repo (lage, root package.json).Screenerrelated dependencies from package.json.yarn.lockfile to removeScreenerdependenciesScreenertags withStoryWrighttags,screenerrelated imports withstorywright.convertscript fromvr-testspackage and invocation of it by therunpublishscreenshottemplate since they are no longer necessary.Related Issue(s)