Document the E2E TransferTransaction tests in test-specifications/.

Problem

The design doc in the repo needs to be updated with latest POC.

Solution

Update the design doc.

Alternatives

No response

Problem

The feedback was that the naming convention used for the server (JSON RPC SERVER) is very similar to the JSON RPC Relay. The ask is to see if we can come up with an alternative name to describe the server if possible to prevent confusion with other Hedera products.

Solution

See above.

Alternatives

No response

Document the E2E FileUpdateTransaction tests in test-specifications/.

Document the E2E AccountAllowanceDeleteTransaction tests in test-specifications/.

Description

The TCK has completed its job. The newest versions of the SDK are falling against some tests. We were thinking that this is a problem with the Local Node, but actually is something with the SDK. We are working with Antonio, Emanuel and me to fix it.

Steps to reproduce

Additional context

No response

Hedera network

testnet

Version

0

Operating system

None

Document the E2E AccountAllowanceApproveTransaction tests in test-specifications/.

Hedera Protobuf: https://github.com/hashgraph/hedera-protobufs/blob/main/services/crypto_approve_allowance.proto

Tests should cover:

• Hbar Allowances
• Non-Fungible Token Allowances
• Fungible Token Allowances

Document the end to end test plan to update an account.

Problem

Document the steps required to complete the TCK project.

Solution

See above.

Alternatives

No response

Document the E2E AccountBalanceQuery tests in test-specifications/.

Document the E2E FileAppendTransaction tests in test-specifications/.

Document tests for getting the account balances.

Hedera Protobufs: https://github.com/hashgraph/hedera-protobufs/blob/main/services/crypto_get_account_balance.proto

Problem

The design image was added to repo as a result of issue #2. However, we also need documentation describing the high level design image.

tck-high-level-design.png

Solution

Add documentation explaining the high level design image.

Define the test driver and what is it accomplishing in the diagram
Define the JSON RPC Server and its role within the context of the diagram
What does current/new version of the SDKs mean?
What does the request bucket mean?
Where are the tests results provided?
What is the test driver response?
what is the SDK JSON RPC Server response?

Alternatives

No response

Problem

All the SDKs should be tested for longevity/stress testing. Currently, the Java and Go SDKs are used in a couple performance benchmark testing suites, however, we need a way to apply the test across all SDKs (Java/JS/Go/C++/Swift/Rust). The TCK design should include a way to test an SDK over a period of time.

Solution

Include SDK longevity testing in the TCK design.

• #32

Alternatives

No response

A longevity test is a type of testing designed to evaluate the long-term stability, performance, and reliability of a software product or system under sustained usage. The primary goal of a longevity test is to identify any issues that may occur when the SDKs are used for an extended period of time.

Key characteristics and objectives of longevity testing include:

Continuous Operation: The SDKs are subjected to continuous operation without interruption. This helps simulate real-world scenarios where SDKs are expected to run for extended periods when creating a large number of transactions.

Stress Testing: Longevity tests include stress testing to push the SDKs to their limits. This helps identify how the SDKs behaves under high loads and whether it can recover from resource constraints.

Cases to consider:

• SDKs can meet the max network wide throttle limits
• SDKs distribute transactions across the network nodes

Performance Metrics: Longevity tests measure and record performance metrics over time to identify any gradual performance degradation. This includes response times, throughput handled, etc.

Error Detection: The tests are designed to detect and log any errors, exceptions, or unexpected behavior that occurs during the extended run. This includes catching and reporting unexpected crashes or exceptions.

Logging and Reporting: Comprehensive logging and reporting mechanisms are put in place to capture all relevant information during the test. This includes error logs, performance reports, and any anomalies detected.

Document the E2E FileDeleteTransaction tests in test-specifications/.

Document the end to end test plan to delete an account allowance.

Hedera Protobuf: https://github.com/hashgraph/hedera-protobufs/blob/main/services/crypto_delete_allowance.proto

Document the E2E AccountInfoQuery tests in test-specifications/.

We need to define the TCK E2E tests the TCK should implement to validate the SDKs work as expected.

Document the E2E FileCreateTransaction tests in test-specifications/.

Problem

Update the readme with the instructions for how to run the TCK project.

Received the following error:
user@admins-Laptop Desktop % cd hedera-sdk-tck-main
user@admins-Laptop hedera-sdk-tck-main % cd test-driver-js
cd: no such file or directory: test-driver-js
user@admins-Laptop hedera-sdk-tck-main %

Solution

Update readme

Alternatives

No response

Document the end to end test plan to create an account.
https://github.com/hashgraph/hedera-sdk-tck/blob/main/test-specifications/createAccount.md