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.

Sign up for GitHub

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

Jump to bottom

Locking an account should have e2e tests - Core 1.0.0 Migration #1022

Closed
faival opened this issue Jul 11, 2018 · 0 comments
Closed

Locking an account should have e2e tests - Core 1.0.0 Migration #1022

faival opened this issue Jul 11, 2018 · 0 comments
Assignees
@faival

Comments

@faival
Copy link
Contributor

faival commented Jul 11, 2018

Expected behaviour

  • locking account feature should work after core 1.0.0 migration

Actual behaviour

  • is not working

Steps to reproduce

  • lock account in settings or wait for timeout to expire. explore redux store and see that the account store still has the passphrase
@faival faival added the chore label Jul 11, 2018
@faival faival self-assigned this Jul 11, 2018
@slaweet slaweet mentioned this issue Jul 11, 2018
Closed
12 tasks
@slaweet slaweet added the test label Jul 12, 2018
This was referenced Jul 12, 2018
Merged
Closed
faival added a commit that referenced this issue Jul 13, 2018
@faival
Merge pull request #1027 from LiskHQ/1022-locking-an-account-should-h…
ffae635 
…ave-e2e-tests-core-1.0.0-migration

Fix remove passphrase when locking an account - Closes #1022
@faival faival closed this as completed Jul 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@faival faival

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@faival @slaweet