Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Scenario: should allow to save account locally is broken #957

Closed
slaweet opened this issue Nov 6, 2017 · 0 comments
Closed

Scenario: should allow to save account locally is broken #957

slaweet opened this issue Nov 6, 2017 · 0 comments
Assignees

Comments

@slaweet
Copy link
Contributor

slaweet commented Nov 6, 2017

Expected behaviour

npm tun e2e-test should end with success

Actual behaviour

npm tun e2e-test ends with

Failures:

1) Scenario: should allow to save account locally, after page reload it should require passphrase to do the first transaction, and remember the passphrase for next transactions - features/accountManagement.feature:2
   Step: And I should see alert dialog with title "Success" and text "Your transaction of 2 LSK to 537318935439898807L was accepted and will be processed in a few seconds." - features/accountManagement.feature:23
   Step Definition: features/step_definitions/generic.step.js:92
   Message:
     AssertionError: inside element ".modal-dialog .alert-dialog-message": expected 'Request is made on the wrong network.' to equal 'Your transaction of 2 LSK to 537318935439898807L was accepted and will be processed in a few seconds.'
         + expected - actual

         -Request is made on the wrong network.
         +Your transaction of 2 LSK to 537318935439898807L was accepted and will be processed in a few seconds.

Steps to reproduce

Run npm tun e2e-test

@slaweet slaweet self-assigned this Nov 6, 2017
slaweet added a commit that referenced this issue Nov 6, 2017
so that everyone can work on other stuff until #957 is fixed
slaweet added a commit that referenced this issue Nov 6, 2017
Fix broken "save account" e2e scenario - Closes #957
@slaweet slaweet closed this as completed in 05e9de9 Nov 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant