From 0b35e137663f5cc4967757d54b7fe5edba41fd17 Mon Sep 17 00:00:00 2001 From: Tanvi Gupta Date: Tue, 16 Oct 2018 01:18:37 +0530 Subject: [PATCH] Added about "Acceptance testing" to article (#18726) --- .../src/pages/guide/english/agile/acceptance-testing/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/client/src/pages/guide/english/agile/acceptance-testing/index.md b/client/src/pages/guide/english/agile/acceptance-testing/index.md index 0c48e4d34b..59623c0634 100644 --- a/client/src/pages/guide/english/agile/acceptance-testing/index.md +++ b/client/src/pages/guide/english/agile/acceptance-testing/index.md @@ -6,6 +6,8 @@ title: Acceptance Testing Acceptance testing, a testing technique performed to determine whether or not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is has met the required criteria for delivery to end users. +In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience.In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. + There are various forms of acceptance testing: ->User acceptance Testing