Testing Relief will save your time and bring more quality into your software product.
...As you make changes in the program code, full testing becomes unnecessary. You only have to test those parts of the program code that were affected by the changes.
Current version is 1.0.1
Learn about all changes in your software product before you start testing it.
...Testing Relief does the expert's work - it analyzes all changes in a software product and detects parts of the program code that depend on these changes, but have not been modified themselves.
To check the reliability of the analysis results, you should make sure that the call graph is built correctly.
If necessary, you should add links between methods manually.
The first thing that you should check is whether the list of methods is displayed on the Not Reached tab.
If the list is not empty, it is necessary to link each of the listed methods to the method that calls it manually and analyze the software product again. The perfect situation is when there are no methods in the Not Reached list or when you are sure that it is not necessary to include methods from the list in the call graph.
The second indicator of the reliability of the analysis results is the test point that contains the Main method. This test point always exists.
Modifications in a software product always affect this test point. If modifications do not affect this test point, you should check the call graph using the Show Call Graph command from the context menu and, if necessary, add links between methods in the software product being tested.
In this case, the TaskVision.Program test point is not affected by the modifications. That is because the handlers of events of the TaskVision.MainForm class are not linked to the constructor of this class. Besides, these handlers are not in the Not Reached list. That is because these handlers are called from other methods in Task Vision or because they are directly specified in the test point and are present on the call graph. You should link them to the TaskVision.MainForm constructor manually since it is logical to assume that if a form has been created, it will be used and, therefore, the handlers of the events triggered by the form will be used. After you make the necessary changes, it is necessary to analyze Task Vision again. You can consider the analysis results as reliable only after you make sure that the call graph is correct.
