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

chore: Jan 20th merging with etc feat branch chore test if all passes #13076

Draft
wants to merge 29 commits into
base: main
Choose a base branch
from

Conversation

EtherWizard33
Copy link
Contributor

@EtherWizard33 EtherWizard33 commented Jan 20, 2025

Description this PR is just to get the sonar diff to run and see if the changes to AccountConnect test in last test are covering what sonar expects

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
@EtherWizard33 EtherWizard33 added Run Smoke E2E Triggers smoke e2e on Bitrise team-wallet-ux labels Jan 20, 2025
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.

Copy link
Contributor

github-actions bot commented Jan 20, 2025

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: bae60d1
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9ce5af29-c649-46fc-b15e-294710feb4cf

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
32.6% Coverage on New Code (required ≥ 60%)

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Run Smoke E2E Triggers smoke e2e on Bitrise team-wallet-ux
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant