Repository navigation
feat(testing): Automated visual diff test report artifacts in GitHub Actions #1363
Description
🎯 Problem Statement & Impact
Upload Percy/Chromatic screenshot diff artifacts to GitHub Actions run summaries.
Prevents regressions, guarantees cross-contract state validity, and validates visual consistency.
🏗️ Technical Architecture & Affected Components
- Primary Component:
e2e/ & integration test harnesses - Integration Points: Ensures full backward compatibility across Soroban contracts, client SDKs, and backend services.
- Resource Management: Optimized memory utilization, efficient state storage keys, and extend_ttl rent management where applicable.
💻 Code Changes & Implementation Steps
- Refactor key modules in
e2e/ & integration test harnessesto fulfill standard code structure guidelines. - Implement explicit validation, error boundaries, and defensive checks.
- Export clean TypeScript bindings or standard Rust/JS interfaces.
- Verify end-to-end compatibility across all environment tiers (local testnet & mainnet).
🧪 Test Strategy & Verification Criteria
- Unit tests cover all primary control branches and edge cases cleanly.
- Integration tests verify contract/API boundaries without memory or balance leaks.
- Automated CI check passes clean linting, formatting, and security audits.
📈 Contribution to Project & Team Growth
Directly enhances platform scalability, user conversion, developer experience, or financial safety across the ecosystem.
Activity
frammawiliansyah commentedon Sep 30, 2026
PR #1412 opened adding visual diff summary generation and artifact publishing to CI workflow.
Reference: #1412
shobhamerabacha-star commentedon Oct 6, 2026
Hello team,
I looked into
feat(testing): Automated visual diff test report artifacts in GitHub Actionsand have an implementation approach ready.Proposed steps:
Let me know if this aligns with the repository guidelines and assign when convenient.
DeFiVC commentedon Oct 20, 2026
@DeFiVC has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeFiVC to this issue.
drips-wave commentedon Oct 20, 2026
Congratulations, @DeFiVC! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @DeFiVC: 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 🌊
drips-wave commentedon Oct 21, 2026
This issue has been completed by @DeFiVC as part of the Stellar Wave Program's 10th Wave 🥳
😎 @DeFiVC: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.