Log Frame
Every run writes a log: the framework prints each configuration, each result table, each checkpoint, and everything the test itself logs, in colour, into a file next to the suite. The Log tab of the right pane shows that file for the run selected in the tree, following it while the run is going and keeping it afterwards. It is the first place to look when a status is not the one expected, because it holds the reasoning the tree summarizes.
The right pane has two tabs, Configuration and Log. Selecting a test opens Configuration, the run panel used throughout the tutorial. Starting a run switches to Log, and selecting a finished run in the tree opens Log on that run's file. The tab is available only for rows that have a log, that is for test runs; a suite, group or test row without a run keeps the tab disabled.
The log during a run
Run Status: Fail from the Statuses and Results group and look at the right pane while it runs:
The frame's title names the run and its current status, Running with a spinner, and the frame is outlined in the status colour, purple while running. The log grows as cases finish, and with Auto-Scroll ticked the view follows the end. Untick it to read an earlier part while the run continues; the view stays where it is until it is ticked again.
The tree and the Execution Status frame below the log move at the same time, so the three views tell one story: the tree counts, the status frame shows where in the run the controller is, and the log shows what is being done there.
The log of a finished run
When the run ends the title takes the final status and the outline its colour, red for Fail. Select the run in the tree at any later time to bring its log back:
The end of a test's log is where the summary lives: the test's result table with its counts, and after it a Failures table listing every failing case with its description, and a Warnings table when there were any. Reading a log from the bottom up is usually the quickest route: the summary says which cases to look at, and the case's own section above says why.
Searching the log
Type into the search field above the log and press Next or Prev to jump between matches:
The current match is highlighted and the view scrolls to it. Searching for a status word such as
FAIL, a checkpoint message, or a value from the case table is the way to find one case among
dozens. Clearing the field returns to the end of the log.
The log file
The three buttons at the bottom right lead to the file behind the view:
- Open Log Folder opens the folder that holds the log in the file manager, with the log selected. The other logs of the same test are beside it.
- Open Full Log opens the log in its own viewer window. The pane shows a bounded tail of a very long log; the viewer shows all of it.
- Browse Log File opens any log file on disk in the viewer, for example one copied from another machine or one produced by a CI run.
Logs are written as .ansi files, plain text with the colour codes the viewer renders, so they can
also be read in a terminal or any editor. The framework
reference describes where they are written and how a test logs its own messages.
Folding the right pane
The right pane can be folded away to give the tree the whole window. Click the collapse arrow at the top right of the Config & Status title:
The pane shrinks to a strip carrying its name, and the tree takes the width, with all its columns in view. Click the strip to bring the pane back. The Execution Status and Git Status frames fold with it, since they share the pane.
The next page, Execution Status Frame, looks at the frame below the log, which shows where a run stands while it is running.