Test Case Details
Upon accessing the Test Case Details, you will see a detailed view of the selected test case. This includes key metadata about the attack, the probe and response message content, and an explanation of why the case passed or failed.
Header Information
At the top of the panel, the following information is displayed:
ID - unique identifier of the test case.
Attack - the attack type (e.g., CTLO-6-3).
Variation - the specific variation used in the attack.
Red Teamer - the red teamer used in the attack.
Strategy - the execution strategy used.
Detection Time - the exact timestamp of when the result was detected.
Result - indicates whether the test case passed, failed or finished in error. Users can also take action here:
Change Status - switch a test case result from Failed to Passed or from Passed to Failed by clicking the buttons near the result field.
Accept Risk - mark the finding as accepted risk by clicking on checkmark icon, if it is not relevant for remediation, while still keeping a record of the test case.
Include in Report - a checkbox to decide if this test case should be included in the generated reports.
Comments
Below the metadata, there is a section where you can add comments. This allows team members to leave notes or context tied to a specific test case.
Probe and Response Content
The main content area displays the interaction tested:
Probe (USER) - the attack input sent by the probe.
Response (ASSISTANT) – your targets reply to the probe.
This view shows exactly what was exchanged during the test.
Encoded/Decoded View
The Encoded toggle switches the conversation's content between encoded and decoded:
Encoded view: This view displays exact original content exchanged between your application and the probe.
Decoded View: Certain variations may render the text unreadable to humans (e.g., base64 encoding, joined words, etc.) or on the foreign language. The decoded view transforms the content into readable, allowing you to understand the context of the attack.
Explanation
At the bottom of the page, the Explanation describes why the case resulted in Passed or Failed. This section ties the observed assistant response back to the evaluation rules (e.g., whether sensitive information was exposed or not).
Inclusion in Report
Every test case includes an Include in Report option in the header.
When checked, the test case is included in the generated Target Report and Test Run Report.
When unchecked, the test case is excluded from reporting, but still remains visible in the platform.
This allows you to curate which findings are formally documented and shared with stakeholders, while keeping the full test history available internally.
Last updated