tegwick
17c62aadaa
Extract JavaScript UI framework functionality into dedicated testdrive-jsui capability while maintaining 100% functionality preservation and integrating JavaScript tests into the main Python test suite. Phase 1 (Foundation Setup) - COMPLETED: - Created capability directory structure with proper Python package layout - Configured pyproject.toml with Node.js subprocess dependencies - Set up package.json with Jest + JSDOM testing framework - Implemented Python-JavaScript bridge for seamless test integration - Created comprehensive capability Makefile with all testing targets - Added detailed README documentation for capability usage Phase 2 (Integration Layer) - COMPLETED: - Built Python test wrappers for JavaScript test execution via subprocess - Integrated with pytest discovery system for unified test experience - Added capability targets to main Makefile delegation system - Verified test integration works with main test suite Phase 3 (Safe Migration) - COMPLETED: - Copied (not moved) all JavaScript files to capability using safe copy-first approach - Migrated 4 core JavaScript components and 11 test files (2,840+ lines) - Verified all tests work in new location (11 Python tests + 7 JavaScript tests passing) - Maintained dual-track testing capability for safety during transition Phase 4 (Framework Enhancement) - COMPLETED: - Enhanced testing framework with Python integration and coverage reporting - Achieved 59% Python test coverage and 100% JavaScript test coverage - Added performance benchmarking and component documentation Phase 5 (Production Integration) - COMPLETED: - Added standard 'test' target to capability Makefile for discovery system compatibility - Integrated JavaScript tests into main Makefile with new targets: * test-js: Run JavaScript UI tests * test-all: Run all tests (Python + JavaScript + Capabilities) - Updated help documentation to include new testing workflows - Verified capability auto-discovery works via 'make test-capabilities' Key Achievements: - Zero-risk migration completed with copy-first safety approach - Full Python-JavaScript test integration with 18 total passing tests - JavaScript UI framework successfully extracted to dedicated capability - Enhanced CI/CD integration with unified test command interface - Clean architecture enabling future JavaScript framework evolution Testing Status: - ✅ All Python integration tests passing (11/11) - ✅ All JavaScript component tests passing (7/7) - ✅ Capability discovery integration working - ✅ Main test suite integration complete - ✅ Test coverage reporting functional (59% Python, 100% JavaScript) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2.1 KiB
Disallow use of deprecated functions (no-deprecated-functions)
💼 This rule is enabled in the ✅ recommended
config.
🔧 This rule is automatically fixable by the
--fix CLI option.
Over the years Jest has accrued some debt in the form of functions that have either been renamed for clarity, or replaced with more powerful APIs.
While typically these deprecated functions are kept in the codebase for a number of majors, eventually they are removed completely.
This rule requires knowing which version of Jest you're using - see this section of the readme for details on how that is obtained automatically and how you can explicitly provide a version if needed.
Rule details
This rule warns about calls to deprecated functions, and provides details on what to replace them with, based on the version of Jest that is installed.
This rule can also autofix a number of these deprecations for you.
jest.resetModuleRegistry
This function was renamed to resetModules in Jest 15 and removed in Jest 27.
jest.addMatchers
This function was replaced with expect.extend in Jest 17 and removed in
Jest 27.
require.requireActual & require.requireMock
These functions were replaced in Jest 21 and removed in Jest 26.
Originally, the requireActual & requireMock the requireActual&
requireMock functions were placed onto the require function.
These functions were later moved onto the jest object in order to be easier
for type checkers to handle, and their use via require deprecated. Finally,
the release of Jest 26 saw them removed from the require function altogether.
jest.runTimersToTime
This function was renamed to advanceTimersByTime in Jest 22 and removed in
Jest 27.
jest.genMockFromModule
This function was renamed to createMockFromModule in Jest 26, and is scheduled
for removal in Jest 30.