Files
markitect-main/capabilities/testdrive-jsui/node_modules/file-entry-cache/changelog.md
tegwick 17c62aadaa feat: complete testdrive-jsui capability extraction with full JavaScript test integration
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>
2025-11-09 22:29:30 +01:00

8.4 KiB

file-entry-cache - Changelog

v6.0.1

v6.0.0

v5.0.1

  • Bug Fixes
    • Fix missing checksum comparison from reconcile since now we use mtime and size by default. - e858aa9, [Roy Riojas](https://github.com/Roy Riojas), 04/02/2019 09:30:22

      Old mode using checkSum can still be used by passing the useCheckSum parameter to the create or createFromFile methods.

v5.0.0

  • Refactoring
    • Make checksum comparison optional - b0f9ae0, [Roy Riojas](https://github.com/Roy Riojas), 03/02/2019 18:17:39

      To determine if a file has changed we were using the checksum in the newer versions, but eslint was relying on the old behavior where we use the mtime and file size to determine if a file changed. That's why we decided to make the checksum check optional.

      To use it:

      // to make the cache use the checkSum check do the following:
      var fCache = fileEntryCache.create(cacheName, dir, useCheckSum); // pass the third parameter as true
      var otherCache = fileEntryCache.createFromFile(cacheName, useCheckSum); // pass the second parameter as true
      

v4.0.0

  • Build Scripts Changes

  • Other changes

    • Remove object-assign dependency. - d0f598e, [Corey Farrell](https://github.com/Corey Farrell), 08/01/2019 20:09:51

      node.js >=4 is required so object-assign is no longer needed, the native Object.assign can be used instead.

v3.0.0

v2.0.0

v1.3.1

v1.3.0

v1.2.4

  • Enhancements

v1.2.3

  • Build Scripts Changes

v1.2.2

  • Build Scripts Changes
    • Add changelogx section to package.json - a3916ff, royriojas, 11/09/2015 16:00:26

v1.2.1

  • Build Scripts Changes

  • Other changes

    • Update dependencies Replaced lodash.assign with smaller object-assign Fixed tests for windows - 0ad3000, [Bogdan Chadkin](https://github.com/Bogdan Chadkin), 11/09/2015 15:44:18

v1.2.0

  • Features
    • analyzeFiles now returns also the files that were removed - 6ac2431, royriojas, 04/09/2015 12:40:53

v1.1.1

v1.1.0