22 April 2024

User Acceptance Testing (UAT)

User Acceptance Testing definition

  • User acceptance testing verifies the user-facing functionality of a software product in real-world scenarios.

User Acceptance Testing purpose

  • With UAT, we’re not just testing if a feature works, we’re testing if it works for the end user.

User Acceptance Testing practice

  • Each user acceptance test reflects the description of a functionality in the software requirements :
    • Scope-wise, UAT strives for a comprehensive coverage of the product in its entirety :
      • This is one of the factors making the task of automating the acceptance testing so difficult.
    • Process-wise, UAT follows system testing :
  • As mentioned earlier, user acceptance testing is the final stage of testing before the software goes live.
    • Running acceptance tests only makes sense after you’ve identified and fixed all major defects during unit and system testing.
    • Automated user acceptance testing can be a part of regression testing where teams rerun UAT suites before major releases.
    • Handwritten user acceptance tests are unproductive
  • The tests written for UAT essentially provide a second layer of coverage on top of what unit tests and integration tests already cover :
    • Basically, we’re talking about 200% test coverage :
      • 100% go for unit and integration tests,
      • and additional 100% are UAT.
    • Writing this much test code is way too time consuming.

More informations for Scrum Testing

More informations for the Scrum PSD certification here.

Leave a Reply

Your email address will not be published. Required fields are marked *