Skip to Content

Changes for page User Acceptance Testing

Last modified by Danniar Firdausy on 2024/09/17 22:01
From version 19.1
edited by Bouke Reitsma
on 2023/06/09 16:14
Change comment: There is no comment for this version
To version 20.1
edited by Bouke Reitsma
on 2023/06/09 16:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,7 +18,7 @@
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