Result Folders

When executing peass, each step creates result folders containing all result data. Some of the results are intended to be used by the end user and others are more debug outputs to find errors in the peass process. In the following, the outputs are documented. $project is the name of your project folder.

Steps

select step

After select, the following files will be present:

• deps_$project.json: the changes selected by static analysis
• execute_$project.json: the changes selected by trace analysis
• temp_$project: temporary dependency files which are created after analyzing part of the project (mainly for debugging purposes)
• views_$project: diffs of the traces of the execution
• properties_$project: methods and method diffs for each method called by a selected test in the version. This folder is necessary for adding the code to the visualization.

measure step

After the measurement, $project_peass will contain two important folders:

• measurementsFull: The measurements of each VM execution. They will be stored in a single KoPeMe-XML file and in single files for each VM invokation in the measurements folder
• logs: The logs of the executions. If unintended functional behavior is observed, this is the first point to look at.

getchanges step

After getChanges, the results folder will contain a file named changes_$project.json, which contains all changes measured in this version. Additionally, in the folder statistics, the results of the measurements will be saved in a JSON-file. If you expected a change and it is not in the changes-file, you should look there. Typical reasons for not finding changes are that the change has not been measured (than it will not be in the statistics-file) or that it has been measured, but the statistical properties are not as expected (in this case, you'll find it in the statistics-file; if e.g. standard deviation is too high, consider higher VM invokation count).

visualizerca step

After visualizerca, the results-folder will contain a folder for each version of your project with HTML files for each executed test in this version. By opening it, you can visualize the call tree and the measured performance values.

Debugging

In case you do not find files in the folders you expect them, or you want a deeper understanding of which (temporary) files are created, have a look at de.peass.dependency.PeASSFolders or de.peass.dependency.CauseSearchFolders.