Implement various scenarios as page routes in tasks-3.0 and tasks-2.0 apps

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, playwright
Domain
testing-qa, web-dev

Research direction

Start by comparing the tasks-3.0 and tasks-2.0 apps and their existing app setup, common code, and Playwright scripts. Identify how routes can represent separate task scenarios while reusing the current setup. Done means both apps expose the planned scenario pages and new Playwright scripts can target those routes without duplicating the shared setup.

Written by the indexing model from the issue text.

Description

We can use routing to define different test case scenarios as pages and reuse the same app setup and common code. Currently, the apps are simple, creating and removing tasks and fetching them through a single method or subscription.

Real-world scenarios will involve more subscriptions, methods, nested reactivity, and additional logic. In future iterations, we can use the same apps with different routes to test more complex scenarios. New Playwright scripts can target these routes while reusing the existing scripts and setup.

Dominant language
JavaScript
Stars
5
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.