review-test-quality

To audit AutoHotkey tests, analyze your test files alongside production source files to detect production logic copies, dead tests, broken assertions, and duplicative tests within the 'tests/' directory. This ensures your AHK test suite accurately reflects actual code behavior.

AutoHotkey test suites pass falsely when tests copy production logic instead of including it, creating tests that verify duplicated code rather than the actual source. Additionally, dead tests with broken assertions that cannot fail will report success regardless of code integrity.

Find stale and duplicative AutoHotkey tests by analyzing test files against current production code to identify redundant tests across different files and detect tests for code paths that no longer exist. This requires comparing unit, GUI, live, and lifecycle test types.

Yes, the AutoHotkey test audit specifically analyzes unit, GUI, live, and lifecycle tests located within the 'tests/' directory. It cross-references these test files with corresponding production source files to identify discrepancies and ensure comprehensive test integrity.

The best way to clean up an AHK test suite before release is performing a comprehensive audit that identifies production code copies, dead tests, duplicative tests, and stale tests. This catches subtle bugs hidden in tests that appear to pass but fail to verify actual code.