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
Add test to confirm preceding child record for HTS transfer #9735
Add test to confirm preceding child record for HTS transfer #9735
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🙌
Signed-off-by: georgi-l95 <glazarov95@gmail.com> apply spotless Signed-off-by: georgi-l95 <glazarov95@gmail.com>
964f879
to
12996b8
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #9735 +/- ##
=============================================
- Coverage 65.44% 65.43% -0.02%
+ Complexity 29983 29981 -2
=============================================
Files 3296 3296
Lines 125494 125558 +64
Branches 13017 13026 +9
=============================================
+ Hits 82130 82154 +24
- Misses 40238 40272 +34
- Partials 3126 3132 +6
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Added new test in the AutoCreationSuite which covers this new case and passes in mono codebase as well. With this change we cover this happy path from issue #9424: A "classic transfer" sending an NFT to an absent receiver address (outside long-zero range) generates a preceding child with a synthetic CryptoCreate and TransactionRecord identical that created by mono-service when it resolves to SUCCESS. Signed-off-by: georgi-l95 <glazarov95@gmail.com> Signed-off-by: Ivo Yankov <ivo@devlabs.bg>
Added new test in the AutoCreationSuite which covers this new case and passes in mono codebase as well. With this change we cover this happy path from issue #9424: A "classic transfer" sending an NFT to an absent receiver address (outside long-zero range) generates a preceding child with a synthetic CryptoCreate and TransactionRecord identical that created by mono-service when it resolves to SUCCESS. Signed-off-by: georgi-l95 <glazarov95@gmail.com> Signed-off-by: Nick Poorman <nick@swirldslabs.com>
Description:
Added new test in the AutoCreationSuite which covers this new case and passes in mono codebase as well.
With this change we cover this happy path from issue #9424:
Related issue(s):
Fixes #
Notes for reviewer:
Checklist