System Integration Testing
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.
Should you have any questions, please contact academy@emagiz.com.
1. Prerequisites
- Basic knowledge of the eMagiz platform
- Understanding of the flow testing functionality
2. Key concepts
This microlearning centers around system integration testing.
By system integration testing we mean: A test that is designed to test whether two systems can communicate via eMagiz in the intended way
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.
3. System Integration Testing
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.
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:
- Unit testing
- Offline testing
- Flow testing
- Integration testing
- Regression testing
- Performance testing
- End-to-end testing (UAT)
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.
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.
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.
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.
4. Key takeaways
- There are various stages of testing
- System Integration Testing (SIT) verifies that all the units that link two systems together work in perfect unison
5. Suggested Additional Readings
If you are interested in this topic and want more information on it please read the following links: