[smoke-test] Test coverage review: 75 source files, 1 test files (1.3%)

Mark commented

2026-05-15 17:20:58 +00:00

Owner

Closing as noise. This issue was auto-filed by a security/smoke scan and is a false positive (package-lock integrity hashes flagged as secrets, stale build artifacts, or trivial coverage reports). Security scanner has been updated to reduce false positives.

Mark added the

blocked:needs-decision

label

2026-05-15 17:20:58 +00:00

Mark commented

2026-05-16 00:33:08 +00:00

Author

Owner

Feature Triage Assessment

Scope: medium
Risk: low
Spec Alignment: misaligned
Summary: Wants to install vitest and write tests to raise test coverage from 1.3% to at least 50% across 71 component files in src/.
Recommendation: Blocked by AGENTS.md directive: 'Do not write tests.' If test coverage is desired, first update AGENTS.md to remove the prohibition and define testing conventions (framework, location, required coverage per file). Then add vitest via npm install -D, create vitest.config.ts, and write tests incrementally starting with utility/lib functions before UI components.
Rationale: Scope is medium — vitest setup touches config files (package.json, vite.config.ts possibly, new vitest.config.ts) and would create many test files. Risk is low — adding tests never touches production logic. But spec is misaligned: AGENTS.md explicitly forbids writing tests ('Do not write tests'), making this request incompatible with current project guidelines. The smoke-test automation filed it without checking the spec constraint.

Labeled blocked:needs-decision — unblock on Forgejo to dispatch to the fixer pipeline.

## Feature Triage Assessment **Scope:** medium **Risk:** low **Spec Alignment:** misaligned **Summary:** Wants to install vitest and write tests to raise test coverage from 1.3% to at least 50% across 71 component files in src/. **Recommendation:** Blocked by AGENTS.md directive: 'Do not write tests.' If test coverage is desired, first update AGENTS.md to remove the prohibition and define testing conventions (framework, location, required coverage per file). Then add vitest via npm install -D, create vitest.config.ts, and write tests incrementally starting with utility/lib functions before UI components. **Rationale:** Scope is medium — vitest setup touches config files (package.json, vite.config.ts possibly, new vitest.config.ts) and would create many test files. Risk is low — adding tests never touches production logic. But spec is misaligned: AGENTS.md explicitly forbids writing tests ('Do not write tests'), making this request incompatible with current project guidelines. The smoke-test automation filed it without checking the spec constraint. Labeled `blocked:needs-decision` — unblock on Forgejo to dispatch to the fixer pipeline.

Mark added the

quickfix

triage-approved

labels

2026-05-17 23:29:23 +00:00

Mark commented

2026-05-19 13:54:19 +00:00

Author

Owner

Closing as noise. This issue was auto-filed by a security/smoke scan and is a false positive (package-lock integrity hashes flagged as secrets, stale build artifacts, or trivial coverage reports). Security scanner has been updated to reduce false positives.

Mark closed this issue

2026-05-19 13:54:19 +00:00

Rows
Columns

[smoke-test] Test coverage review: 75 source files, 1 test files (1.3%) #1

Feature Triage Assessment