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

feat(accountCreateTransaction): Implement AccountCreateTransaction E2E tests: TCK #206

Merged

Conversation

rwalworth
Copy link
Contributor

@rwalworth rwalworth commented May 9, 2024

This PR implements the tests documented in test-specfications/crypto-service/accountCreateTransaction.md. Since some of the work was already done for AccountCreateTransaction tests, this reworks those tests to match what is in the test specifications, in addition to adding any new tests. The docs were also updated to mark the tests as implemented.

Reminder, according to the development process we have established for the TCK (#202), this SHOULD NOT be approved by an SDK lead until their SDK has done any development required to run these tests against their SDK and those tests have passed. Feel free to provide comments and input to the PR, but approvals should not be granted until testing has occurred.

Issues opened in SDKs that encompass the SDK server work should be linked back to the TCK's AccountCreateTransaction development issue (#36) for easy tracking.

Note: This PR contains respective code changes for #209 and #211. If those change, this PR will change.

Related issue(s):

Fixes #205

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

… to use as a model going forward. Create utility.md file to hold miscellaneous JSON RPC functions. Move tests and test specifictions documents to folders for the specific Hedera service they are for

Signed-off-by: Rob Walworth <[email protected]>
…ion is now contained in accountCreateTransaction.md

Signed-off-by: Rob Walworth <[email protected]>
…ix alias only being able to be an ECDSAsecp256k1 key.

Signed-off-by: Rob Walworth <[email protected]>
Signed-off-by: Rob Walworth <[email protected]>
Signed-off-by: Rob Walworth <[email protected]>
Signed-off-by: Rob Walworth <[email protected]>
Signed-off-by: Rob Walworth <[email protected]>
…ts for receiver signature required, auto renew period, and memo

Signed-off-by: Rob Walworth <[email protected]>
@rwalworth rwalworth added the enhancement New feature or request label May 9, 2024
@rwalworth rwalworth self-assigned this May 9, 2024
@rwalworth rwalworth linked an issue May 9, 2024 that may be closed by this pull request
… tests for declineStakingRewards. Some generateKey calls didn't have a type when they should.

Signed-off-by: Rob Walworth <[email protected]>
…t variable name for maxAutoTokenAssociations. Use correct bounds for maxAutoTokenAssociations

Signed-off-by: Rob Walworth <[email protected]>
Copy link

@gsstoykov gsstoykov left a comment

Choose a reason for hiding this comment

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

Regarding test-specifications/crypto-service/ can we think of a better name than crypto-service here? From my perspective this is not that appropriate. Will it be better to have more specific test specification folders like test-specifications/account, test-specifications/contract and etc?

@rwalworth
Copy link
Contributor Author

rwalworth commented Jun 5, 2024

Regarding test-specifications/crypto-service/ can we think of a better name than crypto-service here? From my perspective this is not that appropriate. Will it be better to have more specific test specification folders like test-specifications/account, test-specifications/contract and etc?

Sure, the initial idea was to organize request tests into the Hedera service to which that request was handled (i.e. AccountCreateTransaction into crypto-service, ContractCreateTransaction would be in smart-contract-service, etc.), but I'm not attached to this and am fine with changing it. I can make a separate issue to change the folder names

… maximum auto token associations

The functionality for this will need to be removed when HIP-904 is implemented, as that will make the sender pay at transaction time for the association of a token to a receiver, as opposed to the receiver paying up front at account creation time for all its token assocations.

Signed-off-by: Rob Walworth <[email protected]>
Signed-off-by: Rob Walworth <[email protected]>
Copy link
Contributor

@0xivanov 0xivanov left a comment

Choose a reason for hiding this comment

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

Approving since all the tests are passing in Go and Java

Copy link

@RickyLB RickyLB left a comment

Choose a reason for hiding this comment

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

Tests work with Swift SDK

@rwalworth rwalworth merged commit 040f4a6 into main Aug 6, 2024
3 checks passed
@rwalworth rwalworth deleted the 00205-implement-accountcreatetransaction-e2e-tests-tck branch August 6, 2024 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TCK: Implement tests for AccountCreateTransaction
6 participants