Changes for page User Acceptance Testing

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.marijn
	1	+XWiki.ebakker

Content

...	...	@@ -1,16 +1,9 @@
1		-{{html wiki="true"}}
2		-<div class="ez-academy">
3		- <div class="ez-academy_body">
4		-
5		-<div class="doc">
6		-
7		-
8		-
	1	+{{container}}{{container layoutStyle="columns"}}(((
9	9	= User Acceptance Testing =
10	10
11	11	In this microlearning, we will focus on user acceptance testing. 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.
12	12
13		-Should you have any questions, please contact academy@emagiz.com.
	6	+Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
14	14
15	15	* Last update: April 10th, 2021
16	16	* Required reading time: 4 minutes
...	...	@@ -43,7 +43,7 @@
43	43	* Performance testing
44	44	* End-to-end testing (UAT)
45	45
46		-<p align="center">[[image:intermediate-testing-in-emagiz-user-acceptance-testing--various-steps-of-testing-highlight-uat.png||]]</p>
	39	+[[image:Main.Images.Microlearning.WebHome@intermediate-testing-in-emagiz-user-acceptance-testing--various-steps-of-testing-highlight-uat.png]]
47	47
48	48	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.
49	49
...	...	@@ -53,8 +53,8 @@
53	53
54	54	When you have successfully performed your system integration test you should schedule and execute a user acceptance test (UAT). With this test, the users (business) will test what you (and your team) have built to ensure that it works as expected. A crucial part of this test is user involvement and a focus on functional scenarios. In essence, you should not have to look into eMagiz at this point as your solution should do what it is built for. If you notice that you spend a lot of time in eMagiz while this test is executed you should consider testing your solutions better before going into a user acceptance test (UAT).
55	55
56		-===== Practice =====
57	57
	50	+
58	58	== 4. Assignment ==
59	59
60	60	Browse the internet to learn more about User Acceptance Testing. Use the suggested additional readings as a starting point. Furthermore, see if you and your team members already do this or not.
...	...	@@ -78,9 +78,4 @@
78	78
79	79	As this is a more theoretical microlearning we have no video for this
80	80
81		-</div>
82		-
83		-</div>
84		-</div>
85		-
86		-{{/html}}
	74	+)))((({{toc/}}))){{/container}}{{/container}}