Skip to Content
Version 6.1 by eMagiz on 2022/05/22 21:20
Show last authors
1 {{html wiki="true"}}
2 <div class="ez-academy">
3 <div class="ez-academy_body">
4
5 <div class="doc">
6
7
8
9 = System Integration Testing =
10
11 In this microlearning, we will focus on system integration testing. At some point in time, you have to build your solution and have tested your single unit/flow to see whether or not it works. A logical next step would be to link certain units/flows together to test whether you can communicate via eMagiz between two separate systems. A crucial part of a system integration test is that both the sending and receiving systems are online and ready to produce or consume.
12
13 Should you have any questions, please contact academy@emagiz.com.
14
15 * Last update: April 10th, 2021
16 * Required reading time: 4 minutes
17
18 == 1. Prerequisites ==
19
20 * Basic knowledge of the eMagiz platform
21 * Understanding of the flow testing functionality
22
23 == 2. Key concepts ==
24
25 This microlearning centers around system integration testing.
26
27 By system integration testing we mean: A test that is designed to test whether two systems can communicate via eMagiz in the intended way
28
29 Auditing the eMagiz data models can be done by navigating to the specific data model in question in the Design phase and selecting the button called History located in the bottom bar.
30
31
32
33 == 3. System Integration Testing ==
34
35 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.
36 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:
37
38 * Unit testing
39 * Offline testing
40 * Flow testing
41 * Integration testing
42 * Regression testing
43 * Performance testing
44 * End-to-end testing (UAT)
45
46 <p align="center">[[image:intermediate-testing-in-emagiz-system-integration-testing--various-steps-of-testing-highlight-sit.png||]]</p>
47
48 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.
49
50 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.
51
52 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.
53
54 In other words, a system integration test is designed to test whether two systems can communicate via eMagiz in an intended way. The focus of the system integration test is on the technical part of the integration. In other words, determining that all separate units/flows communicate properly with each other and with the other systems.
55
56 ===== Practice =====
57
58 == 4. Assignment ==
59
60 Browse the internet to learn more about System Integration Testing. Use the suggested additional readings as a starting point. Furthermore, see if you and your team members already do this or not.
61
62 == 5. Key takeaways ==
63
64 * There are various stages of testing
65 * System Integration Testing (SIT) verifies that all the units that link two systems together work in perfect unison
66
67
68
69 == 6. Suggested Additional Readings ==
70
71 If you are interested in this topic and want more information on it please read the following links:
72
73 * https://www.softwaretestinghelp.com/system-integration-testing/
74 * http://tryqa.com/what-is-system-integration-testing/
75
76 == 7. Silent demonstration video ==
77
78 As this is a more theoretical microlearning we have no video for this
79
80 </div>
81
82 </div>
83 </div>
84
85 {{/html}}