Changes for page User Acceptance Testing

Last modified by Danniar Firdausy on 2024/09/17 22:01

From version 21.1
edited by Bouke Reitsma
on 2023/06/09 16:41
Change comment: There is no comment for this version
To version 22.8
edited by Danniar Firdausy
on 2024/09/17 21:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.dfirdausy
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -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.
3 +In this microlearning, we will focus on user acceptance testing. After completing system integration tests, it is time to ensure that your solution meets user expectations and is ready for production. This UAT phase focuses on validating functionality from a business perspective and is key to moving forward confidently.
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -13,7 +13,7 @@
13 13  
14 14  This microlearning centers around user acceptance testing.
15 15  
16 -By user acceptance testing we mean: A test that is designed to let the users (business) test the functionality based on various scenarios. Based on the results of the test you can either go live or need to go back to the drawing board.
16 +* By user acceptance testing we mean: A test that is designed to let the users (business) test the functionality based on various scenarios. Based on the results of the test you can either go live or need to go back to the drawing board.
17 17  
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  
... ... @@ -40,25 +40,20 @@
40 40  
41 41  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).
42 42  
43 -== 4. Assignment ==
43 +== 4. Key takeaways ==
44 44  
45 -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.
45 +* Understanding the different stages of testing (e.g., unit testing, integration testing, and user acceptance testing) is crucial for a successful deployment.
46 +* User Acceptance Testing (UAT) is designed to verify that the solution meets all functional requirements from the perspective of the business users. This ensures that the solution works as expected in real-world scenarios.
47 +* Performing UAT is essential before moving your solution to Production. It helps to confirm that the solution is ready for live use and meets the users’ needs.
46 46  
47 -== 5. Key takeaways ==
49 +== 5. Suggested Additional Readings ==
48 48  
49 -* There are various stages of testing
50 -* User Acceptance Test (UAT) verifies that all intended functional scenarios as devised by the users (business) are indeed working as expected
51 -* You need a User Acceptance Test (UAT) before going live
51 +If you are interested in this topic and want more information, please read the help text provided by eMagiz and see the following links:
52 52  
53 -== 6. Suggested Additional Readings ==
53 +* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
54 +** [[Testing in eMagiz (Explanation)>>Main.eMagiz Academy.Fundamentals.fundamental-testing-in-emagiz.WebHome||target="blank"]]
55 +* [[Acceptance Testing (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22acceptance+testing%22||target="blank"]]
56 +* [[What is user acceptance testing (External)>>https://www.softwaretestinghelp.com/what-is-user-acceptance-testing-uat/||target="blank"]]
57 +* [[User acceptance testing (External)>>https://www.guru99.com/user-acceptance-testing.html||target="blank"]]
54 54  
55 -If you are interested in this topic and want more information on it please read the following links:
56 -
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 -
60 -== 7. Silent demonstration video ==
61 -
62 -As this is a more theoretical microlearning we have no video for this
63 -
64 64  )))((({{toc/}}))){{/container}}{{/container}}