Changes for page User Acceptance Testing

Summary

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

Details

Page properties

Content

...	...	@@ -18,20 +18,20 @@
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
25	25	* Unit testing
26		-* * Offline testing
27		-* * Flow testing
28		-* * Integration testing
	26	+** Offline testing
	27	+** Flow testing
	28	+** Integration testing
29	29	* Regression testing
30	30	* Performance testing
31	31	* End-to-end testing (UAT)
32	32
33		-Add image
34		-
	33	+[[image:Main.Images.Microlearning.WebHome@intermediate-testing-in-emagiz-user-acceptance-testing--various-steps-of-testing-highlight-uat.png]]
	34	+
35	35	An important step is to determine as early as possible the different scenarios which you need to test during your end-to-end test. The earlier you have these clear, the better you can test your changes during the process. This will improve the quality of the integration. Before starting the Create phase, the test scenarios should be agreed upon with the business owners. This is one of the Definition of Done items from the Discovery (Capture & Design) phase we advise.
36	36
37	37	During the development, you have considered what the steps and effects are of the new functionality and change. While implementing, you need to test continuously to verify if the changes made behave as expected. The eMagiz platform offers you features that help you during these tests. While doing development you can use the flow testing functionality in eMagiz to test your small units/flows.
...	...	@@ -54,8 +54,8 @@
54	54
55	55	If you are interested in this topic and want more information on it please read the following links:
56	56
57		-* [[User Acceptance testing 1>>https://www.softwaretestinghelp.com/what-is-user-acceptance-testing-uat/||target="blank"]]
58		-* [[User Acceptance testing 2>https://www.guru99.com/user-acceptance-testing.html||target="blank"]]
	57	+* [[https://www.softwaretestinghelp.com/what-is-user-acceptance-testing-uat/>>https://www.softwaretestinghelp.com/what-is-user-acceptance-testing-uat/||target="blank"]]
	58	+* [[https://www.guru99.com/user-acceptance-testing.html>>https://www.guru99.com/user-acceptance-testing.html||target="blank"]]
59	59
60	60	== 7. Silent demonstration video ==
61	61