Changes for page System Integration Testing
Last modified by Danniar Firdausy on 2024/09/17 21:40
To version 12.7
edited by Danniar Firdausy
on 2024/09/17 21:40
on 2024/09/17 21:40
Change comment:
There is no comment for this version
Summary
-
Page properties (5 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,0 +1,1 @@ 1 +System Integration Testing - Parent
-
... ... @@ -1,0 +1,1 @@ 1 +WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - 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 - In thismicrolearning, we will focuson system integration testing. Atsomepointin time, you have tobuild your solutionand have testedyour singleunit/flow to seewhetherornottworks.Alogicalnextstepwouldbe tolinkcertain units/flows together totestwhetheryoucan communicatevia eMagizbetweentwo 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.3 +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. 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,28 +46,22 @@ 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 43 +== 4. Key takeaways == 49 49 45 +* System Integration Testing (SIT) ensures that individual units or flows work together seamlessly across different systems. 46 +* SIT focuses on verifying technical communication between systems, ensuring data integrity and system dependencies are maintained. 47 +* Early identification of test scenarios improves the quality and reliability of the integration process. 48 +* Successful SIT is essential before moving on to (User) Acceptance Testing to ensure smooth functionality in production environments. 50 50 51 -== 4.Assignment==50 +== 5. Suggested Additional Readings == 52 52 53 - Browsethe internet tolearn moreabout System IntegrationTesting.Use thesuggested additionalreadingsasastartingpoint.Furthermore, see if youandyour team membersalreadydothisornot.52 +If you are interested in this topic and want more information, please read the help text provided by eMagiz and see the following links: 54 54 55 -== 5. Key takeaways == 54 +* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] 55 +** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] 56 +*** [[Understanding Flow Testing (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-understanding-flowtesting||target="blank"]] 57 +* [[Integration Testing (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22integration+testing%22||target="blank"]] 58 +* [[System Integration Testing (External)>>https://www.softwaretestinghelp.com/system-integration-testing/||target="blank"]] 59 +* [[SIT Explained (External)>>http://tryqa.com/what-is-system-integration-testing/||target="blank"]] 56 56 57 -* There are various stages of testing 58 -* System Integration Testing (SIT) verifies that all the units that link two systems together work in perfect unison 59 - 60 - 61 - 62 -== 6. Suggested Additional Readings == 63 - 64 -If you are interested in this topic and want more information on it please read the following links: 65 - 66 -* https://www.softwaretestinghelp.com/system-integration-testing/ 67 -* http://tryqa.com/what-is-system-integration-testing/ 68 - 69 -== 7. Silent demonstration video == 70 - 71 -As this is a more theoretical microlearning we have no video for this 72 - 73 73 )))((({{toc/}}))){{/container}}{{/container}}