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>
97 lines
2.3 KiB
TypeScript
97 lines
2.3 KiB
TypeScript
declare namespace callsites {
|
|
interface CallSite {
|
|
/**
|
|
Returns the value of `this`.
|
|
*/
|
|
getThis(): unknown | undefined;
|
|
|
|
/**
|
|
Returns the type of `this` as a string. This is the name of the function stored in the constructor field of `this`, if available, otherwise the object's `[[Class]]` internal property.
|
|
*/
|
|
getTypeName(): string | null;
|
|
|
|
/**
|
|
Returns the current function.
|
|
*/
|
|
getFunction(): Function | undefined;
|
|
|
|
/**
|
|
Returns the name of the current function, typically its `name` property. If a name property is not available an attempt will be made to try to infer a name from the function's context.
|
|
*/
|
|
getFunctionName(): string | null;
|
|
|
|
/**
|
|
Returns the name of the property of `this` or one of its prototypes that holds the current function.
|
|
*/
|
|
getMethodName(): string | undefined;
|
|
|
|
/**
|
|
Returns the name of the script if this function was defined in a script.
|
|
*/
|
|
getFileName(): string | null;
|
|
|
|
/**
|
|
Returns the current line number if this function was defined in a script.
|
|
*/
|
|
getLineNumber(): number | null;
|
|
|
|
/**
|
|
Returns the current column number if this function was defined in a script.
|
|
*/
|
|
getColumnNumber(): number | null;
|
|
|
|
/**
|
|
Returns a string representing the location where `eval` was called if this function was created using a call to `eval`.
|
|
*/
|
|
getEvalOrigin(): string | undefined;
|
|
|
|
/**
|
|
Returns `true` if this is a top-level invocation, that is, if it's a global object.
|
|
*/
|
|
isToplevel(): boolean;
|
|
|
|
/**
|
|
Returns `true` if this call takes place in code defined by a call to `eval`.
|
|
*/
|
|
isEval(): boolean;
|
|
|
|
/**
|
|
Returns `true` if this call is in native V8 code.
|
|
*/
|
|
isNative(): boolean;
|
|
|
|
/**
|
|
Returns `true` if this is a constructor call.
|
|
*/
|
|
isConstructor(): boolean;
|
|
}
|
|
}
|
|
|
|
declare const callsites: {
|
|
/**
|
|
Get callsites from the V8 stack trace API.
|
|
|
|
@returns An array of `CallSite` objects.
|
|
|
|
@example
|
|
```
|
|
import callsites = require('callsites');
|
|
|
|
function unicorn() {
|
|
console.log(callsites()[0].getFileName());
|
|
//=> '/Users/sindresorhus/dev/callsites/test.js'
|
|
}
|
|
|
|
unicorn();
|
|
```
|
|
*/
|
|
(): callsites.CallSite[];
|
|
|
|
// TODO: Remove this for the next major release, refactor the whole definition to:
|
|
// declare function callsites(): callsites.CallSite[];
|
|
// export = callsites;
|
|
default: typeof callsites;
|
|
};
|
|
|
|
export = callsites;
|