[smoke-test] Test coverage review: 214 source files, 34 test files (15.9%) #226

Closed
opened 2026-05-15 11:45:37 +00:00 by Mark · 2 comments
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.

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.
Author
Owner

GSD RESEARCH could not determine a clear fix.

Here's my analysis of issue #226.


STATUS: UNCLEAR

EVIDENCE: The issue claims 34 test files covering 214 source files (15.9%), but both numbers are inaccurate. The actual repo inventory:

  • Total .py files in repo: 214 (this is the source of the "214 source files" — it's every .py file including scripts and init.py, not just production source)
  • Test files in tests/: 21 .py files, of which 16 are actual test files (excluding init.py, conftest.py)
  • True coverage by issue's own metr
GSD RESEARCH could not determine a clear fix. Here's my analysis of issue #226. --- STATUS: UNCLEAR EVIDENCE: The issue claims 34 test files covering 214 source files (15.9%), but both numbers are inaccurate. The actual repo inventory: - Total .py files in repo: 214 (this is the source of the "214 source files" — it's every .py file including scripts and __init__.py, not just production source) - Test files in tests/: 21 .py files, of which 16 are actual test files (excluding __init__.py, conftest.py) - True coverage by issue's own metr
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.

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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#226
No description provided.