Skip to Content

Changes for page User Acceptance Testing

Last modified by Danniar Firdausy on 2024/09/17 22:01
From version 22.8
edited by Danniar Firdausy
on 2024/09/17 21:49
Change comment: There is no comment for this version
To version 22.9
edited by Danniar Firdausy
on 2024/09/17 22:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
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.
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.
4 4  
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
... ... @@ -15,8 +15,6 @@
15 15  
16 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 -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 -
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.