Conformance Testing of Graph Path

In fact, if there are mergers or derivations, then it will be necessary to test the induced subgraph for conformity. The problem is not to make sure that the path is correct, but to find a way to embed the tools in the system and use them to do this job. There are two main sources of necessary data, and in both cases, you may need to create a reasonably well-designed program, since there is a little likelihood that universal tools provide all the capabilities of your transactions.

What about using exploratory testing services? These are provided to simultaneously learn about the program and perform tests on it. It is a fun approach to testing that allows you to know what the product does and what it does not do.

1. Existing records. Transaction processing systems typically include the transaction record that is required in various applications. For example, account information, security log, backup and repository data. These data are recorded in the nodes, which are often the target of the tester. For example, in data recovery systems, it is common practice to record the structure of all active queues / waiting lines. Before you need to expand the ability to register data in the system, examine all the logs and records required in the application, and consider whether these data can help you test the path you are investigating.
2. Built-in registration. The process of adding the data provided by the application, discussed in the previous paragraph, is conducted to eliminate “blind spots”. Try to limit yourself to minimal additions so that additional data logging does not significantly affect the behavior of the system. As a rule, this is quite feasible, and often the amount of resources sufficient for the most complete registration of transactions does not exceed a few percent of the total available resources. As a rule, such registration capabilities should be built in at once, since it will be very difficult to do this retroactively.
3. Actions in the tracing mode. This is the most pleasant recording method. Transactions may well be performed in the tracing mode. This means that all processes in which these transactions are involved are permanently recorded, as well as all the queues in which they were present. Of course, this capability must also be embedded in the system. Regardless of how much the tracing mode matters to the tester, it is justifiably considered an excellent tool for debugging the system.