E2E tests for subscribe and unlock flow

[aji70]

Description
The goal is to protect critical user flows. Add E2E test: connect wallet (or mock) → subscribe to a creator → unlock one piece of content. Assert UI updates and no errors.

Tasks

• Add E2E framework if missing (e.g. Playwright, Cypress)
• Implement test: connect → subscribe → unlock
• Use testnet or mocked RPC
• Run in CI

Acceptance Criteria

• E2E runs connect → subscribe → unlock
• Test passes in CI
• Flaky failures addressed

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[edehvictor]

@edehvictor has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I work on this? Please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @edehvictor to this issue.

[David-patrick-chuks]

@David-patrick-chuks has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello,
I am a smart contract developer
and i will love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @David-patrick-chuks to this issue.

[Mathews-25]

@Mathews-25 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello maintainer I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mathews-25 to this issue.

[drips-wave]

Congratulations, @Mathews-25! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Mathews-25: 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 issued 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 🌊

[Hahfyeex]

@Hahfyeex has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hahfyeex to this issue.

[studiomonkeyx]

@studiomonkeyx has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

hi, pls let me work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @studiomonkeyx to this issue.

[drips-wave]

Congratulations, @studiomonkeyx! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @studiomonkeyx: 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 issued 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 🌊