test: remove cucumber and all dependencies

[chrisleewilcox]

Description

This commit deletes several outdated feature files related to account actions, browser flow, confirmations, onboarding, performance, security, and wallet functionalities. Additionally, it removes unused step definitions and utility functions to streamline the codebase and improve maintainability.

Changes include:

• Deleted feature files for account actions, importing accounts, and various browser flows.
• Removed step definitions that are no longer referenced in the tests.
• Cleaned up the generateTestReports.js utility function.

This cleanup helps reduce clutter and focuses on maintaining relevant test cases.

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: Remove cucumber test framework from mobile project
  Scenario: Mobile app behaves as expected after removing cucumber
    Given cucumber has been removed from repository
    When user uses mobile app
    Then mobile app behaves as expected

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

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.

---

Note

Remove Cucumber-based E2E tests, configs, and dependencies, updating docs/CI and retaining Detox/Appium flows.

• E2E/Testing:
  • Remove all Cucumber assets: delete wdio/features/**, wdio/step-definitions/**, and wdio/utils/generateTestReports.js.
  • Strip Cucumber config/hooks/reporters from wdio.conf.js; keep spec/junit reporters; clear specs/suites scaffolding.
  • Update BrowserStack/debug configs (wdio/config/*.js) to drop cucumberOpts.tagExpression; keep capability selection via flags (--upgrade, --performance).
• CI (Bitrise):
  • Remove CUCUMBER_TAG_EXPRESSION usage/comments; keep WDIO BrowserStack runners and packaging of reports.
• Docs:
  • Revise E2E docs to Detox/Jest only (remove Cucumber); Appium section trimmed; SampleFeature README now references Detox for E2E.
• Deps/Tooling:
  • Remove Cucumber-related deps and reporters (@wdio/cucumber-framework, cucumber packages, gherkin prettier plugin, multiple-cucumber-html-reporter) and adjust lint-staged (drop *.feature).
  • Clean depcheck ignores to drop Cucumber items; yarn.lock pruned accordingly.

^{Written by Cursor Bugbot for commit 583a040. This will update automatically on new commits. Configure here.}

[github-actions]

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.

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		npm/@jridgewell/[email protected] is a AI-detected potential code anomaly. Notes: The code implements a standard URL parsing and resolution utility with clear responsibilities and deterministic output for valid inputs. The primary security concern is lack of null-checks after regex.exec, which can cause runtime exceptions on malformed inputs. Otherwise, there is no evidence of malicious behavior. Recommended improvement is to guard regex results and validate inputs before accessing groups to prevent crashes and potential abuse. Confidence: 1.00 Severity: 0.60 From: ? → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/@storybook/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/[email protected] → npm/@babel/[email protected] → npm/@react-native/[email protected] → npm/@react-native/[email protected] → npm/[email protected] → npm/[email protected] → npm/@babel/[email protected] → npm/[email protected] → npm/[email protected] → npm/@jridgewell/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@jridgewell/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud