refactor: manipulate entire context instead of TestSetXXX

[hthieu1110]

Linked to #1475

• add testSetContext
• std.TestSetOrigCaller => t.SetPreviousRealm + remove X_testSetOrigCaller
• std.TestSetOrigSend => t.SetOriginSend, testing.SetOriginSend + remove X_testSetOrigSend
• std.TestSetOrigPkgAddr => t/testing.SetOrignalPkgAddress + remove X_testSetOrigPkgAddr
• std.TestSkipHeights => t/testing.SkipHeights + remove TestSkipHeigts
• std.TestSetRealm => t/testing.SetRealm + remove X_testSetRealm
• std.TestIssueCoin => t/testing.IssueCoins

Should we do these refactors in the scope of this PR ?

• implement test banker on Gno side
• implement test log on Gno side

[Gno2D2]

🛠 PR Checks Summary

🔴 Changes to 'docs' folder must be reviewed/authored by at least one devrel and one tech-staff

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• Determine if infra needs to be updated before merging

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)
🔴 Changes to 'docs' folder must be reviewed/authored by at least one devrel and one tech-staff
🟢 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: hthieu1110/gno)

Then

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

Changes to 'docs' folder must be reviewed/authored by at least one devrel and one tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 A changed file matches this pattern: ^docs/ (filename: docs/_assets/minisocial/posts_test-0.gno)

Then

🔴 Requirement not satisfied
└── 🔴 And
    ├── 🟢 Or
    │   ├── 🔴 Pull request author is a member of the team: tech-staff
    │   └── 🟢 At least 1 user(s) of the team tech-staff reviewed pull request(with state "APPROVED")
    └── 🔴 Or
        ├── 🔴 Pull request author is a member of the team: devrels
        └── 🔴 At least 1 user(s) of the team devrels reviewed pull request(with state "APPROVED")

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 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
    └── 🟢 Then
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

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

Determine if infra needs to be updated before merging

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Or
        ├── 🔴 A changed file matches this pattern: Dockerfile
        ├── 🟢 A changed file matches this pattern: ^misc/deployments (filename: misc/deployments/test5.gno.land/genesis_txs.jsonl)
        ├── 🔴 A changed file matches this pattern: ^misc/docker-
        ├── 🔴 A changed file matches this pattern: ^.github/workflows/releaser.*\.yml$
        └── 🔴 A changed file matches this pattern: ^.github/workflows/portal-loop\.yml$

Can be checked by

• team devops

[codecov]

Codecov Report

Attention: Patch coverage is 76.66667% with 14 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
gnovm/tests/stdlibs/testing/context_testing.go	76.27%	12 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!

[leohhhn]

If possible, lets rename and modify t/testing.SkipHeights to SetHeight(), and have it only modify the block number, while having a separate function modify the block timestamp, such as t.SetTimestamp(). This value would be read by time.Now()

Once we get the API down, let me know, and I'll help on modifying the docs for this.

[hthieu1110]

If possible, lets rename and modify t/testing.SkipHeights to SetHeight(), and have it only modify the block number, while having a separate function modify the block timestamp, such as t.SetTimestamp(). This value would be read by time.Now()

Once we get the API down, let me know, and I'll help on modifying the docs for this.

IMHO, SkipHeigh make more sense with current usage and simpler to use because we do not need to get the current height to calculate the "newHeight" to set with SetHeight.

I think we could have SetHeight and SetTimestamp if needed but usages are not the same.

WDYT ? @leohhhn

[thehowl]

can you revert this?

[thehowl]

overall lgtm

[moul]

Suggested change

	func SetOriginCaller(origCaller std.Address) {
	func (c *Context) SetOriginCaller(origCaller std.Address) {

what about doing this, and also adding a func (c Context) String() that we can print?

cc @thehowl

[thehowl]

I'm not sure about the stringer, I think it can already be printed well with fmt.Sprintf("%+v", c)?

Maybe just doing that, not sure.

As for moving to Context, could be good mostly for godoc and "type organization"; in terms of usage, I think most usages would be testing.GetContext().SetXXX, so maybe a bit more verbose.

[moul]

Suggested change

	func SetOriginCaller(origCaller std.Address) {
	ctx := GetContext()
	ctx.OriginCaller = origCaller
	SetContext(ctx)
	}
	func SetOriginCaller(origCaller std.Address) {
	ctx := GetContext()
	ctx.SetOriginCaller(origCaller)
	}
	func (ctx *Context) SetOriginCaller(origCaller std.Address) {
	ctx.OriginCaller = origCaller
	SetContext(ctx)
	}

maybe like this, where top-level funcs are aliases.

[thehowl]

I don't like the aliases and I asked Yo Ha to rollback this; because IMO it adds multiple ways of doing the same thing.