Skip to Content

Changes for page User Acceptance Testing

Last modified by Danniar Firdausy on 2024/09/17 22:01
From version 22.9
edited by Danniar Firdausy
on 2024/09/17 22:01
Change comment: There is no comment for this version
To version 22.6
edited by Danniar Firdausy
on 2024/09/04 16:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,8 +13,10 @@
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 +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 +
18 18  == 3. User Acceptance Testing ==
19 19  
20 20  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.
... ... @@ -40,9 +40,9 @@
40 40  
41 41  == 4. Key takeaways ==
42 42  
43 -* Understanding the different stages of testing (e.g., unit testing, integration testing, and user acceptance testing) is crucial for a successful deployment.
44 -* 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.
45 -* 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.
45 +* There are various stages of testing
46 +* User Acceptance Test (UAT) verifies that all intended functional scenarios as devised by the users (business) are indeed working as expected
47 +* You need a User Acceptance Test (UAT) before going live
46 46  
47 47  == 5. Suggested Additional Readings ==
48 48