#2 Method interactions module report needs to be more verbose

[Peter DePasquale]

When processing sample code, I found that if a method had no interactions, nothing was stated/printed. The module report only stated the method name (e.g. TestClass Method). Something needs to follow it if there is no interaction present, so that it does not look like the report failed. The same thing occurs for classes. See file attachment. Additionally, there is no "graph" created. We should consider adding a graphical representation to the report, but until then we need to change the description in all places it occurs (not just the report...)

[Peter DePasquale]

Sample Report File