15 Years of Good Work

To qualify for the technical interview, you must complete two primary assignments. The first tests your ability to capture requirements in a suitable format, and the second tests your fundamentals on test automation.

Assignment 1

  1. Client Requirement: "We want to create an online marketplace where users can buy and sell products, similar to eBay or Amazon, but we want it to focus on local products and sustainable shopping. Users should be able to search for items, make purchases, leave reviews, and manage their accounts. We also want to have features that promote eco-friendly products."

  Tasks:

  1. Break Down the Requirement into Epics:
    • Identify and outline 3–5 epics based on the given high-level requirement.
    • For each epic, provide a brief description of what it will cover.
  2. Create User Stories for One Epic:
    • Choose one epic from the list you've created.
    • Break this epic down into at least 4-6 user stories.
    • Ensure that each user story follows the format:
    • As a [user role], I want to [do something] so that [benefit].
  3. Write Acceptance Criteria for Two User Stories:
    • Select two user stories from the epic you broke down.
    • Write at least 3-5 acceptance criteria for each user story using the Given-When-Then format (or another clear format if preferred).
  4. Identify Ambiguities and Assumptions:
    • List any assumptions you've made while breaking down the requirement.
    • Identify any areas of ambiguity or missing details that you would need clarification on from the client.

Assignment 1 Submission Guidelines

  1. Provide your work in a structured document (Google Docs, Word, or PDF).
  2. Clearly label each section of the assignment.
  3. You can make reasonable assumptions where necessary but highlight these in your submission.

Assignment 1 Evaluation Criteria

  1. Clarity and Structure: How well the requirement was broken down into epics and user stories.
  2. Completeness: Whether the acceptance criteria are well-defined and cover both happy paths and edge cases.
  3. Critical Thinking: Ability to spot ambiguities and make sensible assumptions.
  4. Focus on Details: Whether the user stories are actionable and focused on delivering value.

Assignment 2

  1. Write automated tests using Playwright and embed both coding and test automation best practices in your automation suite.
  2. Application under test: https://www.saucedemo.com/
  3. Scenarios to be automated
  4. Verify the sorting order displayed for Z-A on the “All Items” page.
  5. Verify the price order (high-low) displayed on the “All Items” page.
  6. Add multiple items to the card and validate the checkout journey.

Bonus points

  1. You have a chance to score bonus points by adding the following additional tests to the above functional tests:
  2. Automated visual tests for the above pages.
  3. Automated accessibility tests for the above pages.

Assignment 2 Submission Guidelines

  1. Create a GitHub repository for your assignment and share the link with us.
  2. Ensure your repository includes:
    • Source code of the automated suite.
    • README.md file with:
      • Instructions on how to set up and run the test locally.
      • A list of prerequisites (e.g., browser version, any dependencies, etc.)
      • Test execution logs/reports: If possible, include generated reports.
  3. An audio-video recording of both headed (browser-based) and headless test execution on your local machine.
  4. Ensure you create a publicly accessible repository so that we can view your work.

Assignment 2 Evaluation Criteria

  1. Code Quality (30%)
    • Modularity & Reusability: Clean, modular, and maintainable code.
    • Readability & Best Practices: Clear naming, consistent formatting, use of Playwright best practices.
    • Error Handling: Anticipates and handles edge cases.
  2. Test Coverage (30%)
    • Required Scenarios: Sorting (Z-A, high-low), cart, and checkout flow.
    • Assertions: Comprehensive and correct assertions.
    • Edge Cases: Considers and tests edge cases.
  3. Bonus Features (20%)
    • Visual Testing: Properly captures layout and handles dynamic content.
    • Accessibility Testing: Covers core accessibility features with actionable results.
  4. GitHub Repository (10%)
    • Structure & Commit History: Organized structure, meaningful commits.
    • README.md: Clear setup, prerequisites, and execution instructions.
  5. Test Execution & Reporting (10%)
    • Headed/Headless Execution: Demonstrated with video recordings.
    • Reports & Logs: Clear reports and useful logs.
  6. Initiative (Optional - 5%)
  7. Extra Efforts: Bonus points for additional tests or optimizations (e.g., CI/CD).

For any doubts or queries, feel free to reach out to our hiring team at [email protected].