Extension-Wallet Testing & Release Prep (E2E + Branding + Docs + Store Assets)

[wheval]

Extension-Wallet Testing & Release Prep (E2E + Branding + Docs + Store Assets)

Description:
Set up end-to-end testing and prepare the extension for release (branding, docs, and store materials).

This task is the MVP subset of Issues #24-28.

Context:
Once the UI exists, we need automated tests and basic release artifacts so changes don’t regress core flows.

Requirements:

• Add Playwright E2E harness with stable fixtures
• Implement minimal E2E scenarios: onboarding + send (happy path)
• Add basic branding assets (icons/logo) placeholders
• Create minimal user documentation pages (GETTING_STARTED + FAQ)
• Add Chrome Web Store listing metadata placeholders

Files to Create:

• apps/extension-wallet/tests/playwright.config.ts
• apps/extension-wallet/tests/e2e/*.spec.ts (minimal scenarios)
• apps/extension-wallet/public/icons/* (placeholders)
• docs/user-guide/GETTING_STARTED.md
• docs/user-guide/FAQ.md
• docs/PRIVACY_POLICY.md
• docs/TERMS_OF_SERVICE.md

Definition of Done:

• pnpm e2e (or test script) runs the minimal scenarios
• Release assets are present and reference correct paths

Labels: extension, testing, release
Estimated Effort: 2–4 days
Priority: Medium

---

Questions or need help?** Join our Telegram community

[opratem]

@opratem has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’d like to work on this issue because it focuses on ensuring the extension wallet is reliable, well tested, and ready for release critical for a seamless user experience and developer confidence.

I have hands on experience across full stack projects, including setting up testing frameworks, managing APIs, and configuring development environments, so I understand the common challenges developers face when running and testing a new codebase.

What stands out in this task is implementing E2E tests with Playwright, creating minimal onboarding and transaction scenarios, and preparing release assets including branding, documentation, and store metadata.

For this task, I will:

Set up a Playwright E2E harness with stable fixtures for onboarding and send flows
Write minimal scenario specs to verify critical user journeys
Prepare placeholder branding assets (icons and logos)
Create user documentation pages (GETTING_STARTED.md, FAQ.md, PRIVACY_POLICY.md, TERMS_OF_SERVICE.md)
Ensure all release assets reference correct paths and implement a simple script to streamline testing

I will ensure the E2E tests are reliable, the documentation is clear, and release assets are fully prepared, so both developers and end users have a smooth, frictionless experience.

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