gjalla-test-audit
Audit Test Suites for False Confidence
Weak tests can hide production bugs while inflating coverage metrics. This skill reviews test quality and identifies misleading, redundant, or excessively mocked tests.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "gjalla-test-audit" from https://skillstore.io/skills/gjalla-gjalla-test-audit.md and its manifest at https://skillstore.io/api/skills/gjalla-gjalla-test-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「gjalla-test-audit」を使用しています。 Audit the account service tests for tautological database mocks.
期待される結果:
Tier 2 finding: three tests return hardcoded database rows and assert those same values. Replace them with database-backed behavior tests.
「gjalla-test-audit」を使用しています。 Find tests that do not exercise production code.
期待される結果:
- Tier 1: The test recreates the source decision logic locally.
- Evidence: The test imports no production module.
- Action: Remove the duplicate logic test after approval and add a source-level test.
「gjalla-test-audit」を使用しています。 Review overlapping unit and integration tests.
期待される結果:
Tier 3 finding: the mocked unit test duplicates the stronger database-backed scenario. Keep unique edge cases and remove redundant coverage after approval.
セキュリティ監査
安全All 15 static findings are false positives caused by Markdown inline-code formatting around test identifiers and examples. The source defines a review workflow and requires approval before cleanup actions. No prompt injection, data exfiltration, command execution, or network reconnaissance intent was found.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/gjalla-gjalla-test-audit/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/gjalla-gjalla-test-audit?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/gjalla-gjalla-test-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/gjalla-gjalla-test-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/gjalla-gjalla-test-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
gjalla. (2026). gjalla-test-audit security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/gjalla-gjalla-test-audit/audits/1BibTeX形式の引用
@techreport{gjalla-gjalla-gjalla-test-audit-2026,
author = {gjalla},
title = {gjalla-test-audit security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/gjalla-gjalla-test-audit/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gjalla-test-audit security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "gjalla"
date-released: "2026-08-11"
url: "https://skillstore.io/skills/gjalla-gjalla-test-audit/audits/1"
identifiers:
- type: other
value: "skillstore:gjalla-gjalla-test-audit:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Review a legacy test suite
Find tests that inflate confidence without protecting current production behavior.
Harden a risky subsystem
Compare critical source paths with tests and identify missing realistic coverage.
Improve quality governance
Classify weak tests and create a prioritized remediation report for the team.
これらのプロンプトを試す
Audit the test suite in [directory]. Identify placeholder tests, tests without source imports, and obvious duplicated coverage. Report findings without changing files.
Review tests for [component]. Compare each test with its source code. Flag tautological mocks and explain which production defects each test cannot detect.
Audit tests covering [critical path]. Rank gaps by production impact, identify encoded bugs, and recommend realistic integration or round-trip tests.
Audit [test scope] across all test layers. Classify findings into deletion and replacement tiers. Estimate coverage impact and propose approved cleanup waves.
ベストプラクティス
- Provide the relevant test files and production source files together.
- Prioritize security boundaries, data access, and core business logic.
- Run tests and coverage between approved cleanup waves.
回避
- Do not judge test quality from coverage percentages alone.
- Do not remove weak tests before identifying replacement coverage.
- Do not classify mocked tests without comparing their behavior to production code.