test(a3p): extend coverage of KREAd app on z:acceptance test phase

[Jorge-Lopes]

closes: https://github.com/Agoric/BytePitchPartnerEng/issues/13
refs: https://github.com/Agoric/BytePitchPartnerEng/issues/9
refs: #10049

Description

The existing test of the KREAd application on the z:acceptance test phase was limited to the feature allowing users to mint a new KREAd Character.

This PR extends the existing test coverage to include the following cases:

• minting a new Character
• unequip all defaults Items
• sell unequipped Item
• buy an Item on marketplace
• sell a Character
• buy a Character on marketplace

Along with the kread.test.js file, this PR includes a new file, /test-lib/kread.js, that provides all the required helper functions for the test cases above, allowing a cleaner and scalable design for KREAd tests.

Since the test coverage of the new file overlaps with the existing one, I opted for removing both:

• create-kread-item-test.sh
• generate-kread-item-request.mjs

Security Considerations

No security considerations were identified.

Scaling Considerations

No scaling considerations were identified.

Documentation Considerations

No documentation considerations were identified.

Testing Considerations

I have confirmed that this works fine with existing a3p tests locally, there is still an improvement that may be useful to ensure that the user wallet's purse balance for the desired KREAd asset was updated accordingly.

For this purpose, we intend to use one feature included in the currently open PR #10171 , which is the sync-tools method retryUntilCondition().

However, we hope to address those changes in a different PR that will be the result of the effort put into the currently open ticket

[Jorge-Lopes]

Since this PR hasn't undergone the review process yet, I’ve decided to close it for the following reasons:

• The PR was opened from a forked repository, while the agreed-upon procedure is to create new branches directly from the agoric-sdk repo. This will help align with the project’s workflow.
• The commit history has become cluttered due to multiple back-and-forth changes, especially around the use of the smallCapsContext method from @agoric/synthetic-chain. Starting fresh will allow me to provide a much cleaner and organized history.

I’ll be submitting a new PR shortly, following the correct workflow and ensuring a clean commit history.