Prompt 12 Test Logs
# prompt-12 — Test Logs
| Attribute | Detail |
| :--- | :--- |
| **Location** | `08-genai-test-acceleration/05-execution-prompts/prompt-12-test-logs.md` |
| **Project** | Tricentis Demo Web Shop |
| **Version** | 1.0 |
| **STLC Phase** | Test Execution |
| **GenAI Technique** | Structured prompt · Iterative HITL |
| **Reference** | CT-GenAI GenAI-2.1.1 / GenAI-2.2.4 |
## Artifact Description
A **Test Log** (**`TL`**) is the chronological record of all events that occurred during a test execution session. According to ISTQB CTFL v4.0, it is a *test execution work product* that documents what happened during the session, including actual results and evidence.
**Role in the STLC:** Provides detailed execution traceability by suite. It is the source of evidence for the Test Summary Report.
**Data sources:** Results from the execution tracker and evidence captured according to the convention in `test-environment-setup.md`.
---
## Prompt
> 🔗 **Requires:** Active `system-prompt.md` + `context-rules.md`. Input: Updated `prompt-11-execution-tracker.md`.
### Instruction
Generate one **`TL`** per suite collaboratively with the tester:
1. For each executed **`TX`**, record: action, actual result, referenced evidence, and status.
2. If the actual result differs from the expected result, mark `FAIL` and request the tester to provide the referenced **`BUG`** ID.
3. Log one suite per **`TL`** — do not mix **`TX`** from different suites in the same **`TL`**.
### Input datawhen to use it
Community prompt sourced from the open-source GitHub repo LuisAdonais/istqb-manual-qa-ecommerce (NOASSERTION). A "Prompt 12 Test Logs" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
LuisAdonais/istqb-manual-qa-ecommerce · NOASSERTION