Changes for page System Integration Testing

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.dfirdausy
	1	+XWiki.eMagiz

Default language

...	...	@@ -1,1 +1,0 @@
1		-en

Content

...	...	@@ -1,9 +1,12 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2	2
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.
	3	+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.
4	4
5	5	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
	7	+* Last update: April 10th, 2021
	8	+* Required reading time: 4 minutes
	9	+
7	7	== 1. Prerequisites ==
8	8
9	9	* Basic knowledge of the eMagiz platform
...	...	@@ -17,6 +17,8 @@
17	17
18	18	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.
19	19
	23	+
	24	+
20	20	== 3. System Integration Testing ==
21	21
22	22	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.
...	...	@@ -23,9 +23,9 @@
23	23	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:
24	24
25	25	* Unit testing
26		- ** Offline testing
27		- ** Flow testing
28		- ** Integration testing
	31	+ * Offline testing
	32	+ * Flow testing
	33	+ * Integration testing
29	29	* Regression testing
30	30	* Performance testing
31	31	* End-to-end testing (UAT)
...	...	@@ -40,22 +40,28 @@
40	40
41	41	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.
42	42
43		-== 4. Key takeaways ==
44	44
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.
49	49
50		-== 5. Suggested Additional Readings ==
	50	+== 4. Assignment ==
51	51
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:
	52	+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.
53	53
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"]]
	54	+== 5. Key takeaways ==
60	60
	56	+* There are various stages of testing
	57	+* System Integration Testing (SIT) verifies that all the units that link two systems together work in perfect unison
	58	+
	59	+
	60	+
	61	+== 6. Suggested Additional Readings ==
	62	+
	63	+If you are interested in this topic and want more information on it please read the following links:
	64	+
	65	+* https://www.softwaretestinghelp.com/system-integration-testing/
	66	+* http://tryqa.com/what-is-system-integration-testing/
	67	+
	68	+== 7. Silent demonstration video ==
	69	+
	70	+As this is a more theoretical microlearning we have no video for this
	71	+
61	61	)))((({{toc/}}))){{/container}}{{/container}}