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

test: jan 29, etc up to date with main merged into chore test if all passes #13249

Conversation

EtherWizard33
Copy link
Contributor

Description

Just a branch to try and get sonar metrics to run, and figure out why they run when they run etc

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

…code) from NetworkVerificationInfo component
…code that ran when feature flag was off (which was now dead code)
…ture flag, remove code that ran when feature flag was off (which was now dead code)
…ks on feature flag, remove code that ran when feature flag was off (which was now dead code)
…e. Update the test to mock nav, and snapshot expected to be updated too.
…tests.

In more detail, after removal of feature flag and corresponding dead code of ff-off, test now runs on ff-on and required update to show content of accordion before asserting, and update snapshot to match new expected rendering.
…t component default style was changed in main
…r multichain and the deadcode behind it.

In the case of this component, it didn't directly have multichain code in it but was rendering a component which did (NetworkVerificationInfo)
… feature flag for multichain and the deadcode behind it.

It needs this since it uses components than end up using NetworkVerificationInfo which had some code toggled on and off based on the multichain feature flag which is being removed in this PR.
…eature flag was ON.

This check on the feature flag was used in some components to render stuff that should render only when the flag was ON.
… since all multichain-permission code is ff-on now
… displayed at initial connection by a dapp.

Main branch has an updted version of this component, that, at the time of initial connection, pre-selects all networks. This is the change reflected in this updated snapshot.
…ions component.

Creating a snapshot on current main with ff-on, matches the expected snapshot when running the test on the feature branch, which has the feature flag and dead code removed. This proves the result in this feature branch is the same currently in prod. Therefore removing the feature flag does not change this component in prod, at least for the state the snapshot captures.
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@EtherWizard33 EtherWizard33 added the No QA Needed Apply this label when your PR does not need any QA effort. label Jan 29, 2025
@EtherWizard33
Copy link
Contributor Author

unused PR, closing

@github-actions github-actions bot locked and limited conversation to collaborators Feb 4, 2025
@EtherWizard33 EtherWizard33 reopened this Feb 4, 2025
@EtherWizard33
Copy link
Contributor Author

definelty closing this PR

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
No QA Needed Apply this label when your PR does not need any QA effort. team-wallet-ux
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants