Skip to Content

Changes for page Queue browser

Last modified by Erik Bakker on 2024/11/24 09:36
From version 13.1
edited by Erik Bakker
on 2023/02/17 16:03
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/02/17 16:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  Please note that this microlearning is for the new monitoring stack only.
5 5  {{/warning}}
6 6  
7 -In this microlearning, we will focus on the queue browser functionality. 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.
7 +In this microlearning, we will focus on the queue browser functionality. This new feature within our 3rd generation runtime allows you to view data flowing through your system. On top of that, it enables you to wiretap information for analysis purposes and even delete messages that should not be in a specific queue.
8 8  
9 9  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
10 10  
... ... @@ -15,53 +15,56 @@
15 15  
16 16  == 2. Key concepts ==
17 17  
18 -This microlearning centers around system integration testing.
18 +This microlearning centers around the queue 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
20 +* The queue browser can be used to view data on the queue
21 +* The queue browser can be used to wiretap a queue to see all future messages (in the next five minutes)
22 +* Message payloads above 100KB are not shown
23 +* The queue browser allows you to delete one (or all) message(s) from the queue
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.
25 +== 3. Queue browser ==
23 23  
24 -== 3. System Integration Testing ==
27 +To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
25 25  
26 -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.
27 -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:
29 +To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
28 28  
29 -* Unit testing
30 - ** Offline testing
31 - ** Flow testing
32 - ** Integration testing
33 -* Regression testing
34 -* Performance testing
35 -* End-to-end testing (UAT)
31 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
36 36  
37 -[[image:Main.Images.Microlearning.WebHome@intermediate-testing-in-emagiz-system-integration-testing--various-steps-of-testing-highlight-sit.png]]
33 +After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option) or that have passed the queue since the moment you activate the option (Wiretap option). For each message, you have various options at your disposal.
38 38  
39 -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.
35 +* Delete the message from the queue (Explore option)
36 +** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue.
37 +* Clear message from the wiretap queue (Wiretap option)
38 +** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview, so it does not clutter the view anymore
39 +* Refresh messages list (both options)
40 +** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
41 +* Save as test message
42 +** 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.
43 +* Download
44 +** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
40 40  
41 -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.
46 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
42 42  
43 -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.
48 +[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
44 44  
45 -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.
50 +{{info}}
51 +The following restrictions apply to this functionality:
52 + * Message payloads above 100KB are not shown in the queue browser as they constitute a "large message."
53 + * The wiretap functionality works for five minutes, during which you can use the refresh button to see new messages coming in.
54 + ** After five minutes, the wiretap functionality will be shut down automatically underwater.
55 + ** To see new messages after five minutes, you must access the wiretap functionality from scratch.
56 +{{/info}}
46 46  
47 -== 4. Assignment ==
48 -
49 -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.
50 -
51 51  == 5. Key takeaways ==
52 52  
53 -* There are various stages of testing
54 -* System Integration Testing (SIT) verifies that all the units that link two systems together work in perfect unison
60 +* The queue browser can be used to view data on the queue
61 +* The queue browser can be used to wiretap a queue to see all future messages (in the next five minutes)
62 +* Message payloads in excess of 100KB are not shown
63 +* The queue browser allows you to delete one (or all) message(s) from the queue
55 55  
56 56  == 6. Suggested Additional Readings ==
57 57  
58 -If you are interested in this topic and want more information on it please read the following links:
67 +If you are interested in this topic and want more information, please read the help texts in eMagiz.
59 59  
60 -* [[System Integration Testing>>https://www.softwaretestinghelp.com/system-integration-testing/||target="blank"]]
61 -* [[SIT Explained>>http://tryqa.com/what-is-system-integration-testing/||target="blank"]]
62 62  
63 -== 7. Silent demonstration video ==
64 -
65 -As this is a more theoretical microlearning we have no video for this
66 -
67 67  )))((({{toc/}}))){{/container}}{{/container}}