From 7281adb56990de78c6702b591bba905cb2a35db6 Mon Sep 17 00:00:00 2001 From: Larry Greene Date: Thu, 8 Nov 2018 08:21:01 +0000 Subject: [PATCH] Removed unnecessary word (#22445) --- guide/english/agile/acceptance-testing/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/agile/acceptance-testing/index.md b/guide/english/agile/acceptance-testing/index.md index 2b737cb194..e1712eacd0 100644 --- a/guide/english/agile/acceptance-testing/index.md +++ b/guide/english/agile/acceptance-testing/index.md @@ -124,7 +124,7 @@ You can write Acceptance Tests for each of these sub-features of the bigger dial - Every time you write a piece of software that will be used again (even by yourself), it helps to write a test for it. When you yourself or another makes changes to this code, running the tests will ensure that you have not broken existing functionality. -- It is usually performed by the users or the Subject Matter Experts. It is also called as User Acceptance Testing (UAT). UAT involves most common real life scenarios. Unlike system testing, it does not focus on the errors or crashes, but on the functionality. UAT is done at the end of the testing life-cycle and will decide if the software is moved to the next environment or not. +- It is usually performed by the users or the Subject Matter Experts. It is also called User Acceptance Testing (UAT). UAT involves most common real life scenarios. Unlike system testing, it does not focus on the errors or crashes, but on the functionality. UAT is done at the end of the testing life-cycle and will decide if the software is moved to the next environment or not. - A good way of defining which acceptance tests should be written is to add acceptance criteria to a user story. With acceptance criteria, you can define when a user story is ready to deploy and the issue completed to your wishes.