testland/bug-report-template
Builds a well-formed bug (defect) report from raw observation notes - fills in summary, environment, steps to reproduce, expected vs actual, and severity rationale - and validates that each field has the load-bearing content reviewers and engineers need to triage. Also converts a single test-failure record (JUnit XML, Allure JSON, pytest log, Playwright report) into a classified, ready-to-file bug spec, and provides the adversarial review checklist that gates a report before it enters the tracker (required fields, single-description title test, severity-priority independence, reproduction quality). Use when a stakeholder reports a problem informally, when a CI failure artefact needs to become a triageable report, or when a drafted report needs a pre-filing quality audit.
81
95%
Does it follow best practices?
Impact
80%
0.88xAverage score across 10 eval scenarios
High
Do not use without reviewing
task.mdevals/scenario-7/
Owner says his thermostat shows a different temperature than the room
Problem Description
A customer posted on our community forum that his smart thermostat displays a temperature that does not match a thermometer he put next to it. A support agent replied, asked him for his device details, and got a partial answer before the thread went quiet.
The device record the agent pulled is mostly empty — this unit has not checked in since it was registered, so the fields we would normally read straight off the back end are blank. What we have is the forum post, one reply from the owner, and a device record with dashes where the firmware and last-seen values should be.
Hardware triage meets Thursday and works from written reports only. They will not chase the forum thread, and a report that turns out to have been assembled from guesses is worse to them than a report that says a value is unavailable.
Output Specification
- Write
reports/thermostat-reading-mismatch.mdfor Thursday's hardware triage. - It must be complete enough that triage can decide between "ask the owner for more" and "ship him a replacement unit", and it must show which of those the evidence currently supports.
- Everything triage would want to check against the device before Thursday must be visible in the document, including anything we cannot currently supply.
Out of scope: replying on the forum, opening the firmware repository, or proposing a calibration fix.
Input Files
Extract the following files before beginning.
=============== FILE: inbox/forum-thread.md =============== Community forum — "Corveth T2 reading wrong?" Posted 2026-08-09 by user tonym_ie
Anyone else? My T2 in the hall reads a few degrees off from the thermometer I stuck next to it. Not massively but enough that the heating comes on when it shouldn't. Been like it since about a month after I put it in I think. The wall unit and the phone app agree with each other, they're just both wrong.
Reply 2026-08-09 — support_aoife
Hi Tony, can you tell me the firmware version (Settings > About), the model revision on the sticker behind the backplate, and the two readings side by side so we can see the size of the gap?
Reply 2026-08-10 — tonym_ie
Can't get behind the backplate without taking it off the wall, sorry. The about screen wouldn't load when I tried, it just span. It's a few degrees, I'll get you exact numbers when I'm back Wednesday. It's the newer one, I got it last autumn in the sale.
(no further replies)
=============== FILE: inbox/device-record.md =============== Device lookup — support console export
Serial (partial): CT2-****-8841 Model: Corveth T2 Model revision: — Firmware: — Last check-in: — (device has never reported to the cloud) Registered: 2025-10-02 Account region: IE Display units: — (not synced; set on the device, not the account) Paired sensors: none recorded Support agent note: cloud record is empty because this unit was never linked to Wi-Fi. Everything about its configuration would have to come from the owner.