- Run the program in debug mode
- Note the code flow path as a result of method allocation
- Change the parameter and run again Program in debug mode
- Repeat the code flow path from the point where the method is applied
- Code flow paths and no Avit Search difference between zero rebel path.
Is there a tool that makes this task easier by recording the code flow path in one file and comparing two such files?
Try something like Emma, this is a unit test code coverage tool, which Can tell you which classes are unused or maintained code paths.
There is a plugin available for eclipse which should provide a pretty brief report.
Occasionally, while debugging the Java code, I do the following to find bugs myself:
Comments
Post a Comment