Changes for page User Acceptance Testing

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -18,7 +18,7 @@
18	18	At some point in time, you have to build your solution and have executed a system integration test. Now it becomes time to include the business (users) with your tests. This is what we call a user acceptance test. The focus of this test is far more functional compared to the system integration test and the goal of the test is to let the business (users) accept the solution. After passing this test you can think about going to Production with the solution.
19	19
20	20	== 3. User Acceptance Testing ==
21		-
	21	+
22	22	The purpose of performing end-to-end testing is to identify system dependencies and to ensure that the data integrity is maintained between various system components and systems. This means that each change made to integration should be tested to make sure that production-like scenarios don’t lead to any unexpected errors when the new functionality is released to production.
23	23	During the development of new features, you will need multiple testing methods. Each method has a different purpose to help you in the different steps of the development process. Not in every case, each test is applicable however they are still recommended. Examples include:
24	24
...	...	@@ -49,7 +49,7 @@
49	49	* There are various stages of testing
50	50	* User Acceptance Test (UAT) verifies that all intended functional scenarios as devised by the users (business) are indeed working as expected
51	51	* You need a User Acceptance Test (UAT) before going live
52		-
	52	+
53	53	== 6. Suggested Additional Readings ==
54	54
55	55	If you are interested in this topic and want more information on it please read the following links: