Changes for page Topic Browser

Summary

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

Details

Page properties

Title

...	...	@@ -1,0 +1,1 @@
	1	+intermediate-testing-in-emagiz-topic-browser

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing in eMagiz.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		-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.
	3	+In this microlearning, we will focus on the topic browser functionality. This powerful new feature within our [[current generation architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] provides visibility into the data flowing through your system, offering the ability to monitor, analyze, and manage messages that utilize the [[event streaming>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming||target="blank"]] functionality. Let's dive into the key concepts and features of this exciting addition!
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
...	...	@@ -15,59 +15,54 @@
15	15
16	16	== 2. Key concepts ==
17	17
18		-This microlearning centers around system integration testing.
	14	+This microlearning centers around the topic browser.
19	19
20		-By system integration testing we mean: A test that is designed to test whether two systems can communicate via eMagiz in the intended way
	16	+* The topic browser can be used to view data on the topic.
21	21
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.
	18	+== 3. Topic browser ==
23	23
	20	+To enhance the observability of your integration landscape while running in the [[current generation architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]], we have added a new feature to our Manage phase called the "Topic browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the topic browser, you can browse your topics as the name suggests.
24	24
	22	+To do so, we show a list of topics belonging to your model you can explore.
25	25
26		-== 3. System Integration Testing ==
	24	+[[image:Main.Images.Release Blog.WebHome@intermediate-testing-in-emagiz-topic-browser--overview.png]]
	25	+
	26	+Per topic, you can zoom in on the partitions of each topic to check out the messages.
27	27
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		-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:
	28	+[[image:Main.Images.Release Blog.WebHome@intermediate-testing-in-emagiz-topic-browser--topic-selected.png]]
30	30
31		-* Unit testing
32		- * Offline testing
33		- * Flow testing
34		- * Integration testing
35		-* Regression testing
36		-* Performance testing
37		-* End-to-end testing (UAT)
	30	+After selecting the topic and choosing the partition, eMagiz will show you the list of messages (latest first) that are currently on the topic. These messages, including headers and envelope, can be viewed by clicking on the message.
38	38
39		-[[image:Main.Images.Microlearning.WebHome@intermediate-testing-in-emagiz-system-integration-testing--various-steps-of-testing-highlight-sit.png]]
	32	+[[image:Main.Images.Release Blog.WebHome@intermediate-testing-in-emagiz-topic-browser--view-messages.png]]
40	40
41		-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.
	34	+On top of that we over the following options.
42	42
43		-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.
	36	+* Save as test message
	37	+** By pressing this button, you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so, we link the message to your model so you can still use it in the flow testing functionality.
	38	+* Download
	39	+** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
44	44
45		-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.
	41	+[[image:Main.Images.Release Blog.WebHome@intermediate-testing-in-emagiz-topic-browser--topic-explorer-options.png]]
46	46
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.
	43	+{{info}}
	44	+* The following restrictions apply to this functionality:
	45	+ ** Messages remain visible in the topic explorer as long as they are not yet deleted based on the retention policy (default of two days)
	46	+ ** To refresh the page you need to go back to the topic overview and open the partition again.
	47	+{{/info}}
48	48
	49	+== 4. Key takeaways ==
49	49
	51	+* The topic browser provides a live view of data within a topic.
	52	+* Messages remain visible in the topic explorer as long as they are not yet deleted based on the retention policy (default of two days)
50	50
51		-== 4. Assignment ==
	54	+== 5. Suggested Additional Readings ==
52	52
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.
	56	+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 ==
	58	+* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
	59	+** [[Traceability in eMagiz (Explanation)>>Main.eMagiz Academy.Fundamentals.fundamental-traceability-in-emagiz||target="blank"]]
	60	+** [[Current Generation Architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
	61	+** [[Event Streaming>>doc:Main.eMagiz Academy.Fundamentals.fundamental-event-streaming||target="blank"]]
	62	+* [[Topic Browser (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=%22topic+browser%22||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}}