HOV QA Engineers
  • πŸ”HOV QA Engineers
  • AGILE TESTING
    • πŸ’»CSS elements for QA
    • πŸ›«On-boarding QA
    • 🀝Testers Communications, Task and Responsibilities
    • ♻️Software Testing Life cycle
    • πŸ““Test Plan
    • 🎟️Kanban board and ticket flows
    • πŸ““User Stories and Acceptance Criteria
    • πŸ‘£Gherkin syntax
    • πŸ€–Test Design
    • πŸ“…Test Strategy
    • πŸ‘¬Types of Testing strategy
    • πŸ§ͺTesting types
    • πŸ›Bug and Bug life Cycle
    • ✍️Manual Testing
    • Automation testing
    • πŸ‘·β€β™‚οΈE2E Testing
    • E2E testing best practices
    • Accessibility testing
    • Performance testing
    • Mobile Testing
  • Tools and Guidelines
    • Software QA Engineer Roadmap
    • πŸ’»Setup Cypress v10 E2E testing
    • πŸ§ͺSetup End to end test with Cypress test suite
    • Setup Performance test with k6
    • API testing with postman
    • Building GitHub Action part 1
    • ✍️Playwright + Cucumber
  • Training Videos
    • SQA Trainings
  • Research
    • πŸ“±Mobile Automation with Appium
      • Setup Project and Configuration (Android)
    • 🎭Playwright - Web Apps E2E Testing Tool
      • Setup Project and Configuration (Android)
    • Testing Library
  • PROJECTS
    • Page 2
    • Opexa
    • πŸ“£Identifi
      • βš–οΈSQA Metrics and Testing progress
      • πŸ§ͺManual testing
        • WEB
          • Sanity Testing
          • Regression Test cases
          • Credentials and URLs
        • Android
          • Sanity Testing
          • Regression Testing
          • End to end Testing
          • Credentials
        • IOS
          • Sanity Testing
          • Regression Testing
      • πŸ“”API Testing
      • πŸ€–Web Automation
        • E2E Automation Test Plan
        • Web Automation Setup
          • 🚧Setup WSL2 Environment for Windows
          • πŸ—οΈSetup local Environment (Linux/Ubuntu)
        • Regression Testing Coverage
        • Sanity Testing Coverage
      • 🎭Performance Testing
        • K6 Test Runs
      • πŸ“΄Mobile Automation
        • Mobile Automation Test Plan
        • Identifi Mobile Automation Setup
      • Page 1
    • πŸ–ΌοΈsubsit
      • Test plan
      • Smoke Test cases
      • πŸ§ͺTest Scenarios
      • πŸ•ΈοΈWeb Automation
    • 🧡ThreadSync
      • Test Plan
    • πŸ‘οΈUpWatch
      • Product Requirement
      • Test plan
      • Monitoring & Bug Reporting
      • E2E Test
        • E2E UpWatch Test
      • E2E QA Automation
    • 🎲Wallet
      • 🧬Test Plan
      • πŸ’»E2E Wallet Automation Test Plan
      • πŸ“–E2E Test Automation Docs
      • πŸ“‘Credentials| Urls
      • πŸ“šWallet Feature List
    • πŸ‘¨β€πŸ’»DevLuvs
      • πŸ§ͺTest Cases
      • πŸ”‘Credentials For Automation
        • πŸ€–Automation Test Cases
      • πŸ“ŠAutomation Board
    • βš™οΈMehira
      • πŸ•ΈοΈWeb Automation
      • Sanity Testing Document
      • How to start running Mehira application from your local using Docker engine via Ubuntu platform
Powered by GitBook
On this page
  1. AGILE TESTING

User Stories and Acceptance Criteria

PreviousKanban board and ticket flowsNextGherkin syntax

Last updated 2 years ago

User story breakdown.

It answers the Questions WHO, WHAT, and WHY. WHO are we building it for? Who is the user?

  • As a <Type of user>

WHAT are we building? What is the intention?

  • I want <Some goal or objective>

WHY are we building it? What is the value fir the customer?

  • So that <benefit/value>

Example: Team Home service Customer Story

WHO are we building it for? Who is the user? WHAT are we building? What is the intention? WHY are we building it? What is the value for the customer?

As a Customer
I want to login into the website
So that I can see deals on services
that I'll need when I move into my new home and I don't have to make dozens of
phone calls to different companies.

Please refer to this document:

πŸ““
https://engineering.hov.co/agile-development/card-management/user-story