Unverified50% confidenceFactExact time
Jest's test.only and its aliases it.only and fit are used to run a subset while debugging; leaving a single .only means the rest of the tests in that file never run, yet the suite still reports green.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen using describe.only in vitest, all tests are still collected, the specified tests are run and the rest are reported as skipped, and the test count does not decrease.70% similarUnverifiedThe results of passing tests and code review are only valid for the specific code version they ran against; once a file changes, the previous evidence no longer describes the current file.64% similarUnverifiedThe explicit exit conditions of the process include: no actionable review findings, the relevant tests run and pass, the verification report passes, the spec/code/tests remain consistent, the final diff has no unexpected changes, and there are no blockers.62% similarUnverifiedThe stopping condition is not the model's self-reported completion, but a state at the product/repository level that can be independently verified by a third party, such as a scripted reload showing the field still exists, a test going from red to green, or a trace reproducing the old failure.62% similarUnverifiedA failing (red) test serves as proof of a bug's existence; when the test turns from red to green, it indicates the issue is resolved and can serve as a regression test to guard the functionality.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1036550API
curl https://kongchang.com/api/v1/knowledge/claims/1036550MCP
get_claim(id=1036550)