Create end-to-end UI test for project token purchase flow

[Josue19-08]

➡️ Title

Create end-to-end UI test for project token purchase flow

📘 Description

Develop UI end-to-end tests to validate the user flow from viewing a project to purchasing its token.

🚀 Requirements

• Test project listing display.
• Test token purchase flow via “Adopt Tree” component.
• Verify UI updates showing purchased tokens in user panel.
• Handle loading, success, and error states in tests.

📝 Implementation notes

• Use existing UI test framework (e.g. Playwright, Cypress).
• Ensure tests are stable, clear, and reproducible.

✅ Acceptance Criteria

• End-to-end UI tests created and passing.
• Covers viewing projects, purchasing tokens, and UI updates.
• Uses kebab-case for all file and folder names.
• Does not use default alias imports or relative paths.
• Uses alias paths with @.
• Code structured with reusable components and reuses existing ones.

⚠ Use kebab-case for all file and folder names.
⚠ Do not use default alias imports or relative paths like ../../components/foo.
⚠ Use alias paths with @, e.g. @/components/foo.
⚠ Structure the code with reusable components and reuse existing ones.

[yhoungdev]

Hey @Josue19-08 is this still open? if yes i would love to jump on it.

[JosueBrenes]

Hi, can i work in this issue? please