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

Increase test coverage for Vault.js #9836

Open
1 of 9 tasks
Gudahtt opened this issue Jun 3, 2024 · 0 comments
Open
1 of 9 tasks

Increase test coverage for Vault.js #9836

Gudahtt opened this issue Jun 3, 2024 · 0 comments
Assignees
Labels

Comments

@Gudahtt
Copy link
Member

Gudahtt commented Jun 3, 2024

What is this about?

The file app/core/Vault.js has poor test coverage. The KeyringController v16 update required changes that further decreased coverage. However, adding more tests was blocked by challenges encountered using KeyringController in a test file.

As of MetaMask/core#4362, we should have an easier time using the KeyringController in unit tests. Once that PR has been merged and released, we should update the KeyringController again in mobile, then follow up with additional unit tests for app/core/Vault.js that increase coverage to 100% for that file.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

Relates to #9570

@Gudahtt Gudahtt self-assigned this Jun 3, 2024
@Gudahtt Gudahtt added the tests Test related issues label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant