System-Test
One of the most time-consuming tasks is testing systems.
Even small changes can lead to the system no longer working as it should.
To eliminate such errors, the java module "system-test" was introduced with OMN-5.12.
It is based on the principle of JUnit 4 and enables testing in an overall environment, regardless of whether the OMN is located locally or at the customer.
Main principle
As already mentioned, the implementation is based on JUnit 4. The difference is that now spring beans are tested instead of classes.
The result is logged on the one hand but also written to an InfluxDB. The InfluxDB is a prerequisite at this point - means without it the test is not executed.
InfluxDB measurements
Measurements are similar to metrics in Grafana. The implementation offers predefined measurements at this point, but they can also be extended by the developer.
Measurement |
Tag: process_id |
Tag: process_name |
Tag: bean_name |
Tag: bean_method |
Tag: status |
Tag: log_level |
Field: duration (long) |
Field: msg (String) |
Identifies the current run by a timestamp |
Self defined name for clustering processes |
Name of the bean which will be executed |
Name of the executed test method |
SUCCESS, ERROR, IGNORE |
INFO, DEBUG, WARN, ERROR |
|||
ost_bean |
required |
required |
required |
required |
required |
|||
ost_bean_method |
required |
required |
required |
required |
required |
required |
||
ost_log |
required |
required |
optional |
optional |
required |
required |
With the help of these measurements you could for example build a Grafana dashboard that looks like this.
