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

Transaction integration tests #301

Merged
merged 11 commits into from
May 23, 2019
Merged

Transaction integration tests #301

merged 11 commits into from
May 23, 2019

Conversation

piotr-iohk
Copy link
Contributor

@piotr-iohk piotr-iohk commented May 22, 2019

Issue Number

Overview

  • I want to add some transaction integration tests for api and cli

Comments

@piotr-iohk piotr-iohk self-assigned this May 22, 2019
("POST", "v2/wallets/" <> widSrc <> "/transactions")
Default payload
verify r
[ expectResponseCode HTTP.status202
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know why this request is giving me 403. Everything works fine with curl....

Copy link
Member

Choose a reason for hiding this comment

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

you can't do multi-output transactions at the moment with those faucet wallets. That's something I wanted to enable yesterday but time flies. Since there's only a single UTxO on the faucet wallet at the moment, you can only have a single output recipient :)
We need to send more than one output on the faucet wallet and have let's say, one million ADA, but not as 1x1M, but 10x100_000 !

--post transaction
r <- request @ApiTransaction ctx ("POST", postTx wa) Default payload
verify r
[ expectResponseCode HTTP.status202
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same here... 403 ¯_(ツ)_/¯

@piotr-iohk piotr-iohk force-pushed the piotr/transaction_tests branch from f4ada18 to 1076b8c Compare May 22, 2019 14:49
@KtorZ KtorZ force-pushed the piotr/transaction_tests branch from 1076b8c to b39bc4a Compare May 22, 2019 16:38
@piotr-iohk piotr-iohk force-pushed the piotr/transaction_tests branch from b39bc4a to 7a54384 Compare May 22, 2019 21:29
@piotr-iohk piotr-iohk marked this pull request as ready for review May 22, 2019 21:31
@piotr-iohk piotr-iohk force-pushed the piotr/transaction_tests branch from 7a54384 to 805def1 Compare May 22, 2019 21:56
@KtorZ KtorZ force-pushed the piotr/transaction_tests branch from 805def1 to 2cbf1b4 Compare May 23, 2019 10:13
Copy link
Member

@KtorZ KtorZ left a comment

Choose a reason for hiding this comment

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

👌

@KtorZ KtorZ force-pushed the piotr/transaction_tests branch from 2cbf1b4 to 2f8ced6 Compare May 23, 2019 10:16
Piotr Stachyra and others added 11 commits May 23, 2019 12:17
Fees are actually not necessarily fixed. They depend on the ix of the input picked. Since we generate all fixture wallets
with an initial transaction with 1K outputs, ix can go from 0 to 999, and therefore be encoded on 1, 2 or 3 bytes. This
depends on which input are assigned to which wallet. As a consequence, it is easier (and more correct) to look at a range
of fees, in case inputs ix gets encoded on 1 or 3 bytes
@KtorZ KtorZ force-pushed the piotr/transaction_tests branch from 2f8ced6 to 6b0e560 Compare May 23, 2019 10:17
@KtorZ KtorZ merged commit ff36343 into master May 23, 2019
@KtorZ KtorZ deleted the piotr/transaction_tests branch May 23, 2019 11:59
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.

2 participants