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>
test-exclude
The file include/exclude logic used by nyc and babel-plugin-istanbul.
Usage
const TestExclude = require('test-exclude');
const exclude = new TestExclude();
if (exclude().shouldInstrument('./foo.js')) {
// let's instrument this file for test coverage!
}
TestExclude(options)
The test-exclude constructor accepts an options object. The defaults are taken from @istanbuljs/schema.
options.cwd
This is the base directory by which all comparisons are performed. Files outside cwd
are not included.
Default: process.cwd()
options.exclude
Array of path globs to be ignored. Note this list does not include node_modules which
is added separately. See @istanbuljs/schema/default-excludes.js for default list.
options.excludeNodeModules
By default node_modules is excluded. Setting this option true allows node_modules
to be included.
options.include
Array of path globs that can be included. By default this is unrestricted giving a result
similar to ['**'] but more optimized.
options.extension
Array of extensions that can be included. This ensures that nyc only attempts to process files which it might understand. Note use of some formats may require adding parser plugins to your nyc or babel configuration.
Default: ['.js', '.cjs', '.mjs', '.ts', '.tsx', '.jsx']
TestExclude#shouldInstrument(filename): boolean
Test if filename matches the rules of this test-exclude instance.
const exclude = new TestExclude();
exclude.shouldInstrument('index.js'); // true
exclude.shouldInstrument('test.js'); // false
exclude.shouldInstrument('README.md'); // false
exclude.shouldInstrument('node_modules/test-exclude/index.js'); // false
In this example code:
index.jsis true because it matches the defaultoptions.extensionlist and is not part of the defaultoptions.excludelist.test.jsis excluded because it matches the defaultoptions.excludelist.README.mdis not matched by the defaultoptions.extensionnode_modules/test-exclude/index.jsis excluded becauseoptions.excludeNodeModulesis true by default.
TestExculde#globSync(cwd = options.cwd): Array[string]
This synchronously retrieves a list of files within cwd which should be instrumented.
Note that setting cwd to a parent of options.cwd is ineffective, this argument can
only be used to further restrict the result.
TestExclude#glob(cwd = options.cwd): Promise<Array[string]>
This function does the same as TestExclude#globSync but does so asynchronously. The
Promise resolves to an Array of strings.
test-exclude for enterprise
Available as part of the Tidelift Subscription.
The maintainers of test-exclude and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.