Skip to Content

Changes for page Testing in eMagiz

Last modified by Erik Bakker on 2024/08/08 11:24
From version 21.1
edited by Bouke Reitsma
on 2023/07/05 11:21
Change comment: There is no comment for this version
To version 16.1
edited by Bouke Reitsma
on 2023/07/05 11:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,7 +35,7 @@
35 35  
36 36  * [[Regression Testing>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing in eMagiz.intermediate-testing-in-emagiz-regression-testing.WebHome||target="blank"]]
37 37  
38 -=== 3.3 Performance Testing ===
38 +==== 3.3 Performance Testing ====
39 39  
40 40  A third method for testing is the performance test. Within a performance test, not the content is important but the amount of load you test on your test subject. In the case of integrations, it means, in general, the number of messages sent over a certain integration. Normally your production environment handles more load than a test or acceptance environment. With a performance test, you can estimate how much impact a new integration has on resources, such as CPU or memory usage of the runtimes within your environment. More information on how to configure the solution architecture of your model can be found in this microlearning:
41 41  
... ... @@ -42,33 +42,23 @@
42 42  * [[Intermediate Solution Architecture>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]
43 43  * [[Advanced Solution Architecture>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]]
44 44  
45 -{{warning}} Performance testing on the eMagiz portal or documentation portal is NOT allowed. {{/warning}}
45 +{{warning}}* Performance testing on the eMagiz portal or documentation portal is NOT allowed. {{/warning}}
46 46  
47 -=== 3.4 End-To-End Testing ===
48 -
49 -The last testing option discussed in this fundamental is a user acceptance test or End-to-End test. In this test, not only developers or testers are involved, but also end-users or other people from the business side. Therefore this testing method is more functionally focused than the previously discussed tests. A User Acceptance test aims to let the business (users) accept the solution created. Normally, this is the last step before pushing the solution to production.
50 -
51 -All the previously mentioned eMagiz functionality helps you complete an End-to-End test or to solve issues found within the test effectively. More information on this testing method can be found in the microlearning:
52 -
53 -* [[User Acceptance Testing>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing in eMagiz.intermediate-testing-in-emagiz-user-acceptance-testing||target="blank"]]
54 -
55 55  == 4. Key takeaways ==
56 56  
57 -* There are different testing methods with different goals
58 -* Not every testing method can be done at any stage of development
59 -* For every testing method, eMagiz has documentation and when possible features to support testing
49 +* Each eMagiz model has a standard Manage phase in which statistics are kept on your environment
50 +* With these statistics, you can determine whether messages have been received by and sent by eMagiz
51 +* This functionality does not allow you to see the content of the messages itself
52 +* On top of that, eMagiz offers Data Sink and long term Archiving as additional licensed features
53 +* Data sink is helpful for an Ops scenario to check whether a specific message is processed by eMagiz (Traceability)
54 +* Long term archiving is helpful for legal purposes as it gives you the option to prove for seven years that a specific message is sent at a specific time (Compliancy)
60 60  
61 61  == 5. Suggested Additional Readings ==
62 62  
63 -If you are interested in this topic and want to learn more on how testing can be done within the eMagiz platform, please check out our microlearnings on testing in eMagiz:
58 +If you are interested in this topic and want to learn how you can control your Cloud with the help of the eMagiz platform, please check out our microlearnings offering on eMagiz Cloud Management:
64 64  
65 -* [[Intermediate Testing in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing in eMagiz.WebHome||target="blank"]]
66 -* [[Advanced Testing in eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Testing in eMagiz.WebHome||target="blank"]]
67 -* [[Crash Course Platfrom>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
68 -* [[Testing API Gateway>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing API Gateway.intermediate-testing-emagiz-api-gateway-testing-api-gateway||target="blank"]]
69 -* [[Regression Testing>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing in eMagiz.intermediate-testing-in-emagiz-regression-testing.WebHome||target="blank"]]
70 -* [[Intermediate Solution Architecture>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Solution Architecture.WebHome||target="blank"]]
71 -* [[Advanced Solution Architecture>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Solution Architecture.WebHome||target="blank"]]
72 -* [[User Acceptance Testing>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Testing in eMagiz.intermediate-testing-in-emagiz-user-acceptance-testing||target="blank"]]
60 +* [[Crashcourse Messaging>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics||target="blank"]]
61 +* [[Data sink>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-data-sink||target="blank"]]
62 +* [[Long term archiving>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Management.advanced-data-management-long-term-archiving||target="blank"]]
73 73  
74 74  )))((({{toc/}}))){{/container}}{{/container}}