Skip to content

Use peerInfo.senderId instead of peerInfo.name to avoid key duplication #4496

Use peerInfo.senderId instead of peerInfo.name to avoid key duplication

Use peerInfo.senderId instead of peerInfo.name to avoid key duplication #4496

Triggered via push March 13, 2024 13:30
Status Success
Total duration 3m 42s
Artifacts

test.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 notices
Feature: Multisig Account Creation Report: src/e2e/features/multisig.feature#L0
βœ… Scenario: User creates a multisig account
Feature: User Onboarding Report: src/e2e/features/onboarding.feature#L0
βœ… Scenario: User creates a new seed phrase account βœ… Scenario: User creates a new seed phrase account βœ… Scenario: User creates a new seed phrase account βœ… Scenario: User creates a new seed phrase account βœ… Scenario: User creates an account with existing seedphrase βœ… Scenario: User creates an account with existing seedphrase βœ… Scenario: User creates an account with existing seedphrase βœ… Scenario: User creates an account with existing seedphrase βœ… Scenario: User creates an account with existing seedphrase - through create new page βœ… Scenario: User creates an account with existing seedphrase - through create new page βœ… Scenario: User creates an account with existing seedphrase - through create new page βœ… Scenario: User creates an account with existing seedphrase - through create new page βœ… Scenario: User imports existing secret key account βœ… Scenario: User imports existing secret key account βœ… Scenario: User imports a backup file βœ… Scenario: User imports a backup file
Feature: Automatic updates Report: src/e2e/features/updates.feature#L0
βœ… Scenario: My account has been topped-up