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

WIP: Two new steps to handle kmd-signing with address #283

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

WIP: Two new steps to handle kmd-signing with address #283

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
630de29
Two new steps to handle kmd-signing with address
May 15, 2023
61d6a8b
Update features/integration/kmd.feature
tzaffi May 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion features/integration/kmd.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,13 +38,15 @@ Feature: KMD
And I import the key
Then the private key should be equal to the exported private key

Scenario Outline: Sign both ways
Scenario Outline: Sign multiple ways
Given an algod v2 client connected to "localhost" port 60000 with token "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
And default transaction with parameters <amt> "<note>"
When I get the private key
And I sign the transaction with the private key
And I sign the transaction with kmd
And I sign the transaction providing the signing address to kmd
Then the signed transaction should equal the kmd signed transaction
Then the signed transaction should equal the signing address kmd signed transaction

Examples:
| amt | note |
Expand Down