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

More tests for byron wallets migration, in particular migrating from big wallets #966

Merged
merged 5 commits into from
Nov 6, 2019

Conversation

KtorZ
Copy link
Member

@KtorZ KtorZ commented Nov 6, 2019

Issue Number

#779

Overview

  • I have added an extra integration scenario to test migrating a big wallet with a lot of dust
  • I have revised byron migrate response behavior when trying to migrate an empty wallet to return a 403. Two reasons for this: this is more semantically correct. It prevents some extra code needed to handle possible errors that could have occurred if we indeed tried migrating (like, an invalid passphrase).
  • enable a currently pending test in BYRON_TX_LIST which required faucet
  • Added extra negative scenario to check migrating with a wrong passphrase
  • Revised endpoints status in swagger.yaml + added missing error code in migration response

Comments

@KtorZ KtorZ requested a review from piotr-iohk November 6, 2019 12:23
@KtorZ KtorZ self-assigned this Nov 6, 2019
Copy link
Contributor

@piotr-iohk piotr-iohk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good.

Updated https://docs.google.com/spreadsheets/d/1fadIA_j4nCd3FbylPo5J8K9Fy6tixSC2T9V3xHKuUvU.
Few more tests could be added though, like verifying behavior when trying to migrate using faulty wallet ids (e.g. trying to migrate Shelly to Byron, or Byron to Byron, or Shelley to Shelley)

@piotr-iohk
Copy link
Contributor

bors r+

iohk-bors bot added a commit that referenced this pull request Nov 6, 2019
966: More tests for byron wallets migration, in particular migrating from big wallets r=piotr-iohk a=KtorZ

# Issue Number

<!-- Put here a reference to the issue this PR relates to and which requirements it tackles -->

#779 

# Overview

<!-- Detail in a few bullet points the work accomplished in this PR -->

- [x] I have added an extra integration scenario to test migrating a big wallet with a lot of dust
- [x] I have revised byron migrate response behavior when trying to migrate an empty wallet to return a 403. Two reasons for this: this is more semantically correct. It prevents some extra code needed to handle possible errors that could have occurred if we indeed tried migrating (like, an invalid passphrase).
- [x] enable a currently pending test in BYRON_TX_LIST which required faucet
- [x] Added extra negative scenario to check migrating with a wrong passphrase 
- [x] Revised endpoints status in swagger.yaml + added missing error code in migration response

# Comments

<!-- Additional comments or screenshots to attach if any -->

<!-- 
Don't forget to:

 ✓ Self-review your changes to make sure nothing unexpected slipped through
 ✓ Assign yourself to the PR
 ✓ Assign one or several reviewer(s)
 ✓ Once created, link this PR to its corresponding ticket
 ✓ Acknowledge any changes required to the Wiki
-->


Co-authored-by: KtorZ <matthias.benkort@gmail.com>
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 6, 2019

Build succeeded

@iohk-bors iohk-bors bot merged commit 732f4a0 into master Nov 6, 2019
@KtorZ KtorZ deleted the KtorZ/byron-big-wallet branch November 6, 2019 13:09
@KtorZ KtorZ added this to the Byron Wallet Support milestone Nov 6, 2019
@@ -1314,7 +1316,7 @@ paths:
tags: ["Byron Transactions"]
summary: List
description: |
<p align="right">status: <strong>under testing</strong></p>
<p align="right">status: <strong>stable</strong></p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants