Log and Outcomes files

CLI (purpleteam) Log Files

Briefly discussed under the PurpleTeam CLI Configure section under loggers.testerProgress.dirname, the CLI writes a log file for each Test Session

Each Tester logs a wealth of information in real-time to the PurpleTeam CLI which is also logged.

The CLI log files are very similar to what you will see in the terminal when running the PurpleTeam CLI in cUi (visual) mode.

At the end of the Test Run each Tester will inform you whether or not your SUT passed and how many defects were found.

Outcomes Files

At the end of the Test Run the orchestrator will collate and package result files (generated by Cucumber) and report files (generated by each Emissary) for each Test Session into an outcomes_[date-time].zip archive and transfer this file to the directory you configured as the outcomes.dir property value in the CLI.

• The App Emissary provides report files in formats: JSON, MD, XML and various HTML as defined by the Job file
• The Tls Emissary provides report files in formats: HTML, JSON, CSV and LOG (the LOG being similar to that displayed in real-time on the CLI terminal and it’s LOG)
• Server Emissary coming soon…

There are details on how to help shape the content of the report files on the Job File page for both BrowserApp and Api under their respective #included sub-sections.

Reading Files

The best way to read the CLI LOG files and any LOG files created by the orchestrator packed into the outcomes_[date-time].zip archive and transferred to the directory you configured as the outcomes.dir property value in the CLI… is with cat, tail (tail <log-file> -f -n +1) and (if properly configured) less, these commands will show the CLI log files properly formatted on your terminal.