System Integration Testing

Last modified by Danniar Firdausy on 2024/09/17 21:40

As you progress in building your solution, you've likely tested individual units or flows to ensure they function correctly. The next logical step is linking these units or flows together to verify that they communicate seamlessly between two separate systems using eMagiz. In this microlearning, we will explore how to perform system integration testing, focusing on ensuring that both the sending and receiving systems work together effectively. 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)

intermediate-testing-in-emagiz-system-integration-testing--various-steps-of-testing-highlight-sit.png

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

  • System Integration Testing (SIT) ensures that individual units or flows work together seamlessly across different systems.
  • SIT focuses on verifying technical communication between systems, ensuring data integrity and system dependencies are maintained.
  • Early identification of test scenarios improves the quality and reliability of the integration process.
  • Successful SIT is essential before moving on to (User) Acceptance Testing to ensure smooth functionality in production environments.

5. Suggested Additional Readings

If you are interested in this topic and want more information, please read the help text provided by eMagiz and see the following links: