Changes for page User Acceptance Testing
Last modified by Danniar Firdausy on 2024/09/17 22:01
From version 10.1
edited by eMagiz
on 2022/06/10 09:09
on 2022/06/10 09:09
Change comment:
There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/08/29 08:32
on 2022/08/29 08:32
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Default language
-
... ... @@ -1,0 +1,1 @@ 1 +en - Content
-
... ... @@ -4,9 +4,6 @@ 4 4 5 5 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 6 6 7 -* Last update: April 10th, 2021 8 -* Required reading time: 4 minutes 9 - 10 10 == 1. Prerequisites == 11 11 12 12 * Basic knowledge of the eMagiz platform ... ... @@ -20,8 +20,6 @@ 20 20 21 21 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. 22 22 23 - 24 - 25 25 == 3. User Acceptance Testing == 26 26 27 27 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. ... ... @@ -28,9 +28,9 @@ 28 28 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: 29 29 30 30 * Unit testing 31 - * Offline testing 32 - * Flow testing 33 - * Integration testing 26 + ** Offline testing 27 + ** Flow testing 28 + ** Integration testing 34 34 * Regression testing 35 35 * Performance testing 36 36 * End-to-end testing (UAT) ... ... @@ -45,8 +45,6 @@ 45 45 46 46 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). 47 47 48 - 49 - 50 50 == 4. Assignment == 51 51 52 52 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. ... ... @@ -57,8 +57,6 @@ 57 57 * User Acceptance Test (UAT) verifies that all intended functional scenarios as devised by the users (business) are indeed working as expected 58 58 * You need a User Acceptance Test (UAT) before going live 59 59 60 - 61 - 62 62 == 6. Suggested Additional Readings == 63 63 64 64 If you are interested in this topic and want more information on it please read the following links: