You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`Passed: 1. Tag/source/owner - saved and searchable.`
36
36
`Failed: 1. Minimal contact fields - not searchable after Save. 2. Full address - not searchable after Save.`
37
-
- Use this table shape for user-facing reports: `Module`, `Issue`, `Description`, `Priority`, `Status`.
37
+
- Use this table shape for user-facing reports: `Module`, `Issue`, `Description`, `Priority`, `Status`, `Screenshot`.
38
38
- Generate Excel only by default. Generate Markdown/JSON only when explicitly requested for debugging or automation.
39
39
- Do not generate CSV.
40
40
- Excel first sheet must be `Bug Report` with only user-facing bug rows.
41
41
- Excel second sheet should be `Summary`; technical evidence sheets can follow after that.
42
42
- Excel reports should be readable without manual fixing: set practical column widths, wrap text, use dynamic row heights, freeze/filter headers, and color header/priority/status cells.
43
43
- Aggregate repeated duplicate bugs into one clear row. Do not repeat the same bug 10 times unless each row is materially different.
44
44
- Excel reports must embed screenshots/images in the workbook when screenshots exist.
45
+
- The first `Bug Report` sheet must include a `Screenshot` column. If an issue has screenshot evidence, place the image directly inside that row's screenshot cell, not only in a separate screenshots sheet.
45
46
- Do not push reports, screenshots, logs, traces, or `.env` files to GitHub.
46
47
- Use browser state indexes when selector guessing is uncertain.
Excel is the default user-facing artifact. The first sheet must be `Bug Report` with the clean issue table only. The second sheet should be `Summary`. Technical evidence sheets can follow after that. Screenshots are embedded in the workbook when available. Excel must be readable without manual resizing: practical widths, wrapped text, dynamic row heights, frozen/filterable headers, and colored header/priority/status cells.
65
+
Excel is the default user-facing artifact. The first sheet must be `Bug Report` with the clean issue table only. The second sheet should be `Summary`. Technical evidence sheets can follow after that. Screenshots are embedded in the workbook when available. The first `Bug Report` sheet must include a `Screenshot` column and embed each issue screenshot directly in that row's screenshot cell when evidence exists. Excel must be readable without manual resizing: practical widths, wrapped text, dynamic row heights, frozen/filterable headers, and colored header/priority/status cells.
66
66
67
67
Repeated duplicate bugs should be aggregated into one clear row. Keep raw evidence in the technical sheets instead of making the user-facing bug table noisy.
Copy file name to clipboardExpand all lines: agent/src/api-agent/groq-tool-loop.ts
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,8 @@ export async function runGroqToolLoop(task: QaTask, headed: boolean, maxSteps: n
47
47
"Inspect icon-only controls by SVG/title/aria/parent button metadata; delete may be an unlabeled trash icon in a detail drawer bottom action area.",
48
48
"Ask before confirming a destructive alternative such as Archive when Delete is unavailable unless explicitly allowed.",
49
49
"User-facing reports are Excel-only by default unless the task explicitly asks for Markdown or JSON.",
50
-
"The first Excel sheet must be a clean bug report with Module, Issue, Description, Priority, Status.",
50
+
"The first Excel sheet must be a clean bug report with Module, Issue, Description, Priority, Status, Screenshot.",
51
+
"If an issue has screenshot evidence, embed the image directly in that issue row's Screenshot cell on the Bug Report sheet.",
51
52
"Excel reports must be readable without manual resizing: wrapped text, useful widths/heights, frozen headers, and colored headers/priority/status cells.",
52
53
"Do not generate CSV reports.",
53
54
"Do not push reports, screenshots, logs, or local artifacts to GitHub.",
Copy file name to clipboardExpand all lines: agent/tests/smoke.ts
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -68,19 +68,22 @@ async function main(): Promise<void> {
68
68
title: "Some lead conditions do not persist",
69
69
severity: "High",
70
70
area: "Lead Module",
71
-
description: "Result: 1/5 lead conditions saved.\nPassed:\n1. Tag/source/owner - saved and searchable.\nFailed:\n1. Minimal contact fields - not searchable after Save."
71
+
description: "Result: 1/5 lead conditions saved.\nPassed:\n1. Tag/source/owner - saved and searchable.\nFailed:\n1. Minimal contact fields - not searchable after Save.",
`Passed: 1. Tag/source/owner - saved and searchable.`
41
41
`Failed: 1. Minimal contact fields - not searchable after Save. 2. Full address - not searchable after Save.`
42
-
- Use this table shape for user-facing reports: `Module`, `Issue`, `Description`, `Priority`, `Status`.
42
+
- Use this table shape for user-facing reports: `Module`, `Issue`, `Description`, `Priority`, `Status`, `Screenshot`.
43
43
- Generate Excel only by default. Generate Markdown/JSON only when explicitly requested for debugging or automation.
44
44
- Do not generate CSV.
45
45
- Excel first sheet must be `Bug Report` with only user-facing bug rows.
46
46
- Excel second sheet should be `Summary`; technical evidence and coverage sheets can follow after that.
47
47
- Excel reports should be readable without manual fixing: practical column widths, wrapped text, dynamic row heights, frozen/filter headers, and colored header/priority/status cells.
48
48
- Aggregate repeated duplicate bugs into one clear row. Do not repeat the same bug many times unless each row is materially different.
49
49
- Excel reports must embed screenshots/images in the workbook when screenshots exist.
50
+
- The first `Bug Report` sheet must include a `Screenshot` column. If an issue has screenshot evidence, place the image directly inside that row's screenshot cell, not only in a separate screenshots sheet.
50
51
- Reports must include coverage truth: modules/scopes tested, actions attempted, evidence, status, blockers, and confidence.
51
52
- Do not push reports, screenshots, logs, traces, browser state, or `.env` files to GitHub.
0 commit comments