I am currently running the Java test cases inside the "soot-info-flow" module of FlowDorid. I just wanted to know how we can instrument the test codes so that I can insert a Jimple code into the original Jimple output for adding conditional statements as sinks. And if I instrument the code will it affect the access path mechanism deployed by FlowDroid? and is the access path mechanism the main contributor towards finding leakages in an application?
You can use the PreAnalysisHandler to inject code instrumentation into the analysis (have a look at SetupApplication.addPreprocessor()). The access paths have nothing to do with the instrumentation part.
Dear Steven
I am currently running the Java test cases inside the "soot-info-flow" module of FlowDorid. I just wanted to know how we can instrument the test codes so that I can insert a Jimple code into the original Jimple output for adding conditional statements as sinks. And if I instrument the code will it affect the access path mechanism deployed by FlowDroid? and is the access path mechanism the main contributor towards finding leakages in an application?