Test Execution Log Template (ISO/IEC/IEEE 29119-3)
Per-run execution log: run header, time-ordered entries with impact, reconciled run summary
Anleitung: Use it for every manual test run, or around an automated run. Fill the run header first and write entries as events happen. The main pitfall is logging only verdicts and leaving out restarts and deviations.
Vorschau
Test Execution Log: [Run ID] [Test item and build]
Chronological log of one test run: what was executed, when, by whom, on which build and environment, and every event that matters for reading the results. The entry fields follow the test execution log information item of ISO/IEC/IEEE 29119-3:2021 (clause 8.10: unique identifier, date and time, description, impact). Replace every
[bracketed]value and every row marked Example.
Run header
| Field | Value |
|---|---|
| Run ID | [R-0312] (Example) |
| Test procedure or suite | [TP-PDF-03, PDF export procedures] (Example) |
| Test item and build | [Quillfern Desk 5.3.0-rc2] (Example) |
| Environment | [ST-2, see TER-01 to TER-06] (Example) |
| Data set | [TDR-03] (Example) |
| Tester(s) | [@tester] |
| Start and end | YYYY-MM-DD HH:MM to HH:MM [time zone] |
Log entries
| Entry ID | Date and time | Description | Impact |
|---|---|---|---|
| R-0312-01 (Example) | YYYY-MM-DD 09:02 | Smoke suite passed on rc2; data set TDR-03 restored from snapshot | None |
| R-0312-02 (Example) | YYYY-MM-DD 09:15 | TC-PDF-031 to TC-PDF-033 executed: passed | None |
| R-0312-03 (Example) | YYYY-MM-DD 09:41 | TC-PDF-034 step 4: export of 5.4 MB history failed after 60 s; incident INC-QD53-0147 raised | Test failed; large-file cases paused |
| R-0312-04 (Example) | YYYY-MM-DD 10:05 | Procedure deviation: TC-PDF-036 run with a 4.8 MB history instead of 5 MB, approved by [@test-lead] | Result valid for files under 5 MB only |
| R-0312-05 (Example) | YYYY-MM-DD 11:30 | ST-2 restarted by platform team for an unrelated change; 12 minutes downtime | Two cases repeated after restart |
| R-0312-06 (Example) | YYYY-MM-DD 12:10 | Run ended; remaining large-file cases deferred to retest after INC-QD53-0147 | Run incomplete |
| [R-nnnn-nn] | [Date and time] | [Event] | [Impact] |
Run summary
| Planned | Executed | Passed | Failed | Blocked | Not run |
|---|---|---|---|---|---|
| Example: 8 | 5 | 4 | 1 | 0 | 3 |
Incidents raised: [INC-QD53-0147]. Results recorded in: [test
management tool link]. Reported in: Test Status Report
(quality/test-status-report). Incident form: Test Incident Report
(quality/test-incident-report).
Standard and licence note
Structure aligned with ISO/IEC/IEEE 29119-3:2021, Software and systems engineering: Software testing: Part 3: Test documentation, test execution log information item (clause 8.10). The standard is copyrighted and is cited by name, edition and clause number only; all wording here is original. Official text: ISO, IEC and IEEE, purchase or licensed access: https://www.iso.org/standard/79429.html. Template licence: MIT.
Ähnliche Vorlagen
Exploratory Test Charter Template (Session-Based)
Session-based exploratory testing: charter and mission, session sheet with time split and notes, bugs and issues, debrief
Test & QualitätOrganizational Test Policy Template (ISO/IEC/IEEE 29119-3)
Organisation test policy: objectives, test process, organisation, training, ethics, standards, value measures, archiving, improvement, exceptions
Test & QualitätPerformance Test Plan and Report Template
Performance plan and report: SLAs classified by ISO/IEC 25010:2023, workload mix, Little's law sizing, load, stress, soak and spike tests, percentiles, bottlenecks