You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write contracts/docs/testing.md: how the Soroban test environment is used across the three contracts — Env::default(), address generation, mock_all_auths versus asserting real auth, advancing ledger time for expiry paths, and cross-contract test setup where proposals calls into group_treasury.
Acceptance criteria:
Documents the standard test scaffolding with a copyable example
Explains testing authorization properly, and the risk that blanket auth mocking hides a missing require_auth
Documents how to test time-dependent behaviour such as proposal expiry
Documents the test_snapshots/ directory: what generates it, that it is committed, and that it is Prettier-ignored as generated output
Congratulations, @G-ELM! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @G-ELM: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @G-ELM: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
G-ELM commentedon Aug 30, 2026
@G-ELM has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @G-ELM to this issue.
drips-wave commentedon Aug 30, 2026
Congratulations, @G-ELM! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @G-ELM: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
github-actions commentedon Aug 30, 2026
Closed by #594, merged into
dev.drips-wave commentedon Aug 30, 2026
This issue has been completed by @G-ELM as part of the Stellar Wave Program's 8th Wave 🥳
😎 @G-ELM: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.