tegwick
1358ca17ec
Some checks failed
Test Suite / unit-tests (3.11) (push) Has been cancelled
Test Suite / unit-tests (3.12) (push) Has been cancelled
Test Suite / integration-tests (push) Has been cancelled
Test Suite / e2e-tests (push) Has been cancelled
Test Suite / performance-tests (push) Has been cancelled
Test Suite / code-quality (push) Has been cancelled
Test Suite / security-scan (push) Has been cancelled
Test Suite / test-summary (push) Has been cancelled
Clean up test infrastructure by removing problematic tests that create circular dependencies and execute the test suite from within tests. Key removals: - Delete test_issue_57_test_efficiency_improvements.py entirely (12 tests) - Contained tests that ran `make test-tdd`, `make test-status` etc. - Created circular dependencies where tests execute the entire test suite - Violated separation of concerns between testing and test infrastructure - Remove self-execution blocks from 11 test files - Eliminated `if __name__ == '__main__': pytest.main([__file__, '-v'])` patterns - Prevents confusion and potential circular execution paths - Test files should be run via pytest, not as standalone scripts Test Infrastructure Improvements: - Reduced test count from 701 to 689 tests (removed 12 problematic tests) - Eliminated subprocess calls to `make test-*` commands from within tests - Removed `pytest.main()` calls that could cause circular execution - Maintained clean separation between test infrastructure and actual tests Impact: - No more tests testing tests (circular dependency elimination) - Cleaner test execution without subprocess complexity - Proper test isolation and independence - Faster and more reliable test runs The proper way to test infrastructure is to test the underlying functions directly, not to execute the entire test suite from within a test. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>