Changes for page User Acceptance Testing

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Regression Testing
	1	+User Acceptance Testing

Content

...	...	@@ -1,6 +1,6 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2	2
3		-In this microlearning, we will focus on regression testing. At some point in time, you have build a large integration model with multiple complex flows. Some of these flows might be unintentially impacted by changes submitted to these flows. Therefore, you want to keep testing whether existing functionality is not impacted. This is called a regression test. When successfully conducting regression test you can be sure that it is save to deploy your solution on Production without impacting your existing integrations. The main functionality to do this within eMagiz is the automated flow test, which we will disucss in detail.
	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
...	...	@@ -11,57 +11,51 @@
11	11
12	12	== 2. Key concepts ==
13	13
14		-This microlearning centers around regression testing.
	14	+This microlearning centers around user acceptance testing.
15	15
16		-By user regression testing we mean: A test that is designed to verify whether existing functionality is not impacted by newly added functions.
	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 build a large integration model with multiple complex flows. Some of these flows might be unintentially impacted by changes submitted to these flows. Therefore, you want to keep testing whether existing functionality is not impacted. This is called a regression test. When successfully conducting regression test you can be sure that it is save to deploy your solution on Production without impacting your existing integrations. The main functionality to do this within eMagiz is the automated flow test, which we will disucss in detail.
	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		-== 3. Automated flow test ==
	20	+== 3. User Acceptance Testing ==
21	21
22		-The purpose of automated flow tests is to prevent undesired impact on flows when applying certain changes. Everytime a new version of a flow is submitted, automated flow tests will be exectuded. This way, you can verify whether changes in the flow did not introduce problems on exisiting requirements. The remainder of this section will explain how to setup a automated flow test.
23		-
24		-//__Configuration__//
25		-To configure an automated flow test, you can select the option automated test case by opening the Details pop-up of a test case.
	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	+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:
26	26
27		-[[image:Main.Images.Release Blog.WebHome@177-release-blog-1.jpg]]
28		-
29		-When choosing the option Yes and pressing Save, the overview of flow tests will reflect this change by showing an icon in front of the test case.
	25	+* Unit testing
	26	+* * Offline testing
	27	+* * Flow testing
	28	+* * Integration testing
	29	+* Regression testing
	30	+* Performance testing
	31	+* End-to-end testing (UAT)
30	30
31		-
32		-[[image:Main.Images.Release Blog.WebHome@177-release-blog-2.jpg]]
	33	+Add image
33	33
34		-After configuring this, eMagiz will automatically execute the test case(s) upon creating a new version. This process happens in the background, so you don’t have to wait for it to finish.
	35	+An important step is to determine as early as possible the different scenarios which you need to test during your end-to-end test. The earlier you have these clear, the better you can test your changes during the process. This will improve the quality of the integration. Before starting the Create phase, the test scenarios should be agreed upon with the business owners. This is one of the Definition of Done items from the Discovery (Capture & Design) phase we advise.
35	35
36		-//__Analysis on flow level__//
37		-To see the results of the automated flow test(s) on flow level, you can navigate to the History tab. Here you will see the overall test status (of all the test cases combined), and it provides you with a button to Show the specific test results.
	37	+During the development, you have considered what the steps and effects are of the new functionality and change. While implementing, you need to test continuously to verify if the changes made behave as expected. The eMagiz platform offers you features that help you during these tests. While doing development you can use the flow testing functionality in eMagiz to test your small units/flows.
38	38
39		-[[image:Main.Images.Release Blog.WebHome@177-release-blog-3.jpg]]
	39	+However, at some point, you need to link these units/flows together. That is when you as a developer should want to do a system integration testing to determine for yourselves that everything that you and others within the team have worked to connect two systems works across all those scenarios. This way you know that this solution is ready for (User) Acceptance Testing.
40	40
41		-//__Analysis on release level__//
42		-On top of that, eMagiz will show you an overview for all flows in your release, whether the test cases have failed, are still running, have no tests in them, or whether the test cases within a flow all passed. This overview is shown whenever you want to deploy or make a new release active.
43		-
44		-[[image:Main.Images.Release Blog.WebHome@177-release-blog-4.jpg]]
45		-
46		-Note that you can always view the test results overview of any older release by navigating to the Details pop-up and selecting the Test results tab.
47		-
48		-[[image:Main.Images.Release Blog.WebHome@177-release-blog-5.jpg]]
	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).
49	49
50	50	== 4. Assignment ==
51	51
52		-Open a flow within your model and configure an automated flow test.
	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.
53	53
54	54	== 5. Key takeaways ==
55	55
56	56	* There are various stages of testing
57		-* Regression testing test whether existing functionality is not impacted by new changes
58		-* Automated flow test is a functionality within eMagiz to conduct regression tests
59		-
	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
	52	+
60	60	== 6. Suggested Additional Readings ==
61	61
62	62	If you are interested in this topic and want more information on it please read the following links:
63	63
64		-* [[Regression testing>>https://www.guru99.com/regression-testing.html||target="blank"]]
	57	+* [[User Acceptance testing 1>>https://www.softwaretestinghelp.com/what-is-user-acceptance-testing-uat/||target="blank"]]
	58	+* [[User Acceptance testing 2>https://www.guru99.com/user-acceptance-testing.html||target="blank"]]
65	65
66	66	== 7. Silent demonstration video ==
67	67