QA
Senior~90 minFramework designConfigPage ObjectsFixturesTest dataCI

Build the TrendKart framework from scratch

App: TrendKart, a practice fashion marketplace (Myntra-style). Login: Guest checkout works; members: arya@trendkart.test / Trendy@123 or register. REST API: tests call it as /api/... through the request fixture or page.request; GET /api lists every endpoint ↗.

Interview scenario

"Here is an empty folder and TrendKart. Set up the automation framework you would put in front of a client: Playwright config, page objects, an API client where the app has an API, fixtures, test data, production-grade UI and API tests, and a README. Treat it like a real repo, not an exercise. Search, filters, sorting and the bag; make the suite data-driven."

Acceptance criteria

  1. playwright.config.ts you write yourself: testDir, baseURL from an environment variable with a default, retries, reporter, trace/screenshot on failure.
  2. pages/ with at least two page objects; fixtures.ts that extends test (for example a logged-in page or a ready page object).
  3. tests/ with at least two spec files and four tests in total, using only fixtures and page objects, grouped with test.describe or tagged @smoke/@regression.
  4. data/ or utils/ for test data and helpers; a README that says how to install and run.
  5. Where the application has a REST API (the practice apps, OrangeHRM, AutomationExercise): an API client module, at least one API spec, and a spec that uses the API to set up or verify a UI journey. UI-only frameworks do not pass.
  6. Everything green: in the browser for the practice apps, and on GitHub Actions with your own config for every app.

🔒 This framework workspace is part of Architect

Architect unlocks the live editor, the production-grade framework review and the reference frameworks for all 6 workspaces, on top of every lab and interview answer. One payment of ₹1,599, lifetime access. Already on a lower tier? Upgrade for the difference.