The activity starts with manual analysis of specification of the system under test (SUT). All the requirements are considered with respect to system description in order to select possible performance/security risks stemming from unexpected (temporary or permanent) network conditions.

These cases are described in a formal way from different points of view of which network conditions are needed to be examined and how they relate to each other. The number of all possible combinations of different network parameters will possibly be high so an optimised plan is required.

The optimisation of the fault injection plan (i.e., the plan which different faults aka. network conditions are needed to be examined) is performed by combinatorial testing technique (e.g. pair-wise testing). Combinatorial optimisation is fully automated.

The optimised fault-injection plan needs to be perfomed. The next set of faults are selected (Simulated Faults Selection) and configured (Network Fault Injection) in simulated network link(s), The test case is setup (SUT Infrastructure Setup) with re-linking the original network link with simulated (fault-injected) network link and the test case is executed while the SUT performance is automatically monitored. Monitoring is performed by runtime verification method based on formal specification. Runtime verification is performed by Plogchecker tool which monitors the trace of events in the SUT's log file.

If all the faults and their combinations are examined, the aggregated performance report is being transferred as a result of the method.