Skip to Content

Changes for page Queue browser

Last modified by Erik Bakker on 2024/11/24 09:36
From version 7.1
edited by Erik Bakker
on 2022/06/10 08:38
Change comment: Imported from XAR
To version 10.1
edited by Erik Bakker
on 2022/08/29 08:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +System Integration Testing
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -1,13 +1,9 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -= System Integration Testing =
3 3  
4 4  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.
5 5  
6 6  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 -* Last update: April 10th, 2021
9 -* Required reading time: 4 minutes
10 -
11 11  == 1. Prerequisites ==
12 12  
13 13  * Basic knowledge of the eMagiz platform
... ... @@ -21,8 +21,6 @@
21 21  
22 22  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.
23 23  
24 -
25 -
26 26  == 3. System Integration Testing ==
27 27  
28 28  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.
... ... @@ -29,9 +29,9 @@
29 29  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:
30 30  
31 31  * Unit testing
32 - * Offline testing
33 - * Flow testing
34 - * Integration testing
26 + ** Offline testing
27 + ** Flow testing
28 + ** Integration testing
35 35  * Regression testing
36 36  * Performance testing
37 37  * End-to-end testing (UAT)
... ... @@ -46,8 +46,6 @@
46 46  
47 47  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.
48 48  
49 -
50 -
51 51  == 4. Assignment ==
52 52  
53 53  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.
... ... @@ -57,8 +57,6 @@
57 57  * There are various stages of testing
58 58  * System Integration Testing (SIT) verifies that all the units that link two systems together work in perfect unison
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: