Test Quality Evaluator FAQs

Question 1

Which programming languages and frameworks does it support?

Accepted Answer

While it can evaluate general testing logic, it provides specialized guidance for Go (table-driven tests), Playwright (E2E), React (component testing), and standard HTTP API handlers.

Question 2

Can it help me find missing test cases?

Accepted Answer

Yes, part of the evaluation workflow involves a coverage gap analysis where it identifies public methods, error paths, and edge cases in your source code that lack corresponding tests.

Question 3

How does it identify 'brittle' tests?

Accepted Answer

It looks for tests that assert on internal implementation details, such as checking if a specific internal function was called, rather than asserting on the final outcome or state change.

Question 4

Why does the skill prioritize integration over mocking?

Accepted Answer

The core philosophy is that tests should exercise real behavior. Over-mocking often results in tests that pass even when the system is broken; integration tests ensure components work together as intended.

Question 5

Does this skill actually run my test suite?

Accepted Answer

No, this skill performs a static analysis of your test code and source code to evaluate the logic, architecture, and efficacy of your tests without executing them.

Test Quality Evaluator

主要功能

使用场景

Test Quality Evaluator

主要功能

使用场景