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

[e2e] Signature redesign - Create tests to check info per signature type #23977

Closed
6 tasks
digiwand opened this issue Apr 11, 2024 · 1 comment · Fixed by #24352
Closed
6 tasks

[e2e] Signature redesign - Create tests to check info per signature type #23977

digiwand opened this issue Apr 11, 2024 · 1 comment · Fixed by #24352
Assignees
Labels
INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. release-12.0.0 team-confirmations Push issues to confirmations team team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead

Comments

@digiwand
Copy link
Contributor

digiwand commented Apr 11, 2024

ref: #23552 (comment)
Blocked By: #24712

Create e2e tests:

  • Signature domain section (per signature type)
    • Request from displays the url with HTTP warning if using HTTP instead of HTTPS
    • Interacting with displays the verifying contract address
  • Signature message section (per signature type)
    • Primary type is correctly displayed
    • Message info matches the one we pass on the test dapp (no missing fields, correct identation etc)
@digiwand digiwand added the team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead label Apr 11, 2024
@metamaskbot metamaskbot added the INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. label Apr 11, 2024
@cryptotavares cryptotavares added the team-confirmations Push issues to confirmations team label Apr 24, 2024
@cryptotavares
Copy link
Contributor

Hey team! Please add your planning poker estimate with Zenhub @digiwand @jpuri @pedronfigueiredo

@digiwand digiwand self-assigned this Apr 30, 2024
digiwand added a commit that referenced this issue Jun 3, 2024
…24352)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24352?quickstart=1)

## **Related issues**

Fixes: #23977
Blocked By: #24712

## **Manual testing steps**


1. set `ENABLE_CONFIRMATION_REDESIGN=true` in .metamaskrc
2. enable Experimental > "Improved signature requests" in settings
3. test signatures in [test-dapp](https://metamask.github.io/test-dapp/)

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [ ] 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](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
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.

---------

Co-authored-by: Priya Narayanaswamy <priya.narayanaswamy@consensys.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
INVALID-ISSUE-TEMPLATE Issue's body doesn't match any issue template. release-12.0.0 team-confirmations Push issues to confirmations team team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants