feat(gnovm): Result Caching for filetest

[notJoon]

Description

Cache the test results for filetest. For *_test.gno files, caching has not yet been implemented since previous test execution results can sometimes affect other tests.

1. Test Result Caching:
   • Cached results are reused when test file content remains unchanged
   • Cache is stored in the ~/.gno-test-cache directory
2. Cache Invalidation:
   • Automatically invalidated cache when test file content changes
   • Cache usage can be completely disabled with the -no-cache flag ¹

Usage

Run the test command as you would for a regular test execution when not using the no-cache option.

gno test <test_path> -v

When running the same test more than once without any modifications, it will be marked as CACHED as shown below. (Using the p/demo/avl package as an example.)

$ gno test examples/gno.land/p/demo/avl/node_test.gno -v

...
=== RUN   TestTreeReverseIterateByOffset
--- PASS: TestTreeReverseIterateByOffset (0.00s)
=== RUN   file/z_0_filetest.gno
=== CACHED file/z_0_filetest.gno (0.01s)
false 2
=== RUN   file/z_1_filetest.gno
=== CACHED file/z_1_filetest.gno (0.01s)
false 3
=== RUN   file/z_2_filetest.gno
=== CACHED file/z_2_filetest.gno (0.01s)
false 3
ok      examples/gno.land/p/demo/avl    1.18s

To disable caching, add the -no-cache flag as shown below:

gno test <test_path> -v -no-cache

$ gno test examples/gno.land/p/demo/avl/node_test.gno -v -no-cache

...
--- PASS: TestTreeIterateByOffset (0.00s)
=== RUN   TestTreeReverseIterateByOffset
--- PASS: TestTreeReverseIterateByOffset (0.00s)
=== RUN   file/z_0_filetest.gno
false 2
--- PASS: file/z_0_filetest.gno (0.01s)
=== RUN   file/z_1_filetest.gno
false 3
--- PASS: file/z_1_filetest.gno (0.02s)
=== RUN   file/z_2_filetest.gno
false 3
--- PASS: file/z_2_filetest.gno (0.02s)
ok      examples/gno.land/p/demo/avl    1.39s

Footnotes

1. While Go doesn't have a no-cache flag, the idiomatic approach is to use -count 1. ↩

[Gno2D2]

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: notJoon/gno-core)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least 1 user(s) of the organization reviewed the pull request (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            └── 🔴 On no pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[codecov]

Codecov Report

Attention: Patch coverage is 51.44928% with 67 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
gnovm/pkg/test/cache.go	51.37%	38 Missing and 15 partials ⚠️
gnovm/pkg/test/test.go	33.33%	11 Missing and 3 partials ⚠️

📢 Thoughts on this report? Let us know!

[jefft0]

@notJoon , please add tests to fix the failed codecov CI check.