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>
109 lines
2.8 KiB
Markdown
109 lines
2.8 KiB
Markdown
# jest-docblock
|
|
|
|
`jest-docblock` is a package that can extract and parse a specially-formatted comment called a "docblock" at the top of a file.
|
|
|
|
A docblock looks like this:
|
|
|
|
```js
|
|
/**
|
|
* Stuff goes here!
|
|
*/
|
|
```
|
|
|
|
Docblocks can contain pragmas, which are words prefixed by `@`:
|
|
|
|
```js
|
|
/**
|
|
* Pragma incoming!
|
|
*
|
|
* @flow
|
|
*/
|
|
```
|
|
|
|
Pragmas can also take arguments:
|
|
|
|
```js
|
|
/**
|
|
* Check this out:
|
|
*
|
|
* @myPragma it is so cool
|
|
*/
|
|
```
|
|
|
|
`jest-docblock` can:
|
|
|
|
- extract the docblock from some code as a string
|
|
- parse a docblock string's pragmas into an object
|
|
- print an object and some comments back to a string
|
|
|
|
## Installation
|
|
|
|
```sh
|
|
# with yarn
|
|
$ yarn add jest-docblock
|
|
# with npm
|
|
$ npm install jest-docblock
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const code = `
|
|
/**
|
|
* Everything is awesome!
|
|
*
|
|
* @everything is:awesome
|
|
* @flow
|
|
*/
|
|
|
|
export const everything = Object.create(null);
|
|
export default function isAwesome(something) {
|
|
return something === everything;
|
|
}
|
|
`;
|
|
|
|
const {
|
|
extract,
|
|
strip,
|
|
parse,
|
|
parseWithComments,
|
|
print,
|
|
} = require('jest-docblock');
|
|
|
|
const docblock = extract(code);
|
|
console.log(docblock); // "/**\n * Everything is awesome!\n * \n * @everything is:awesome\n * @flow\n */"
|
|
|
|
const stripped = strip(code);
|
|
console.log(stripped); // "export const everything = Object.create(null);\n export default function isAwesome(something) {\n return something === everything;\n }"
|
|
|
|
const pragmas = parse(docblock);
|
|
console.log(pragmas); // { everything: "is:awesome", flow: "" }
|
|
|
|
const parsed = parseWithComments(docblock);
|
|
console.log(parsed); // { comments: "Everything is awesome!", pragmas: { everything: "is:awesome", flow: "" } }
|
|
|
|
console.log(print({pragmas, comments: 'hi!'})); // /**\n * hi!\n *\n * @everything is:awesome\n * @flow\n */;
|
|
```
|
|
|
|
## API Documentation
|
|
|
|
### `extract(contents: string): string`
|
|
|
|
Extracts a docblock from some file contents. Returns the docblock contained in `contents`. If `contents` did not contain a docblock, it will return the empty string (`""`).
|
|
|
|
### `strip(contents: string): string`
|
|
|
|
Strips the top docblock from a file and return the result. If a file does not have a docblock at the top, then return the file unchanged.
|
|
|
|
### `parse(docblock: string): {[key: string]: string | string[] }`
|
|
|
|
Parses the pragmas in a docblock string into an object whose keys are the pragma tags and whose values are the arguments to those pragmas.
|
|
|
|
### `parseWithComments(docblock: string): { comments: string, pragmas: {[key: string]: string | string[]} }`
|
|
|
|
Similar to `parse` except this method also returns the comments from the docblock. Useful when used with `print()`.
|
|
|
|
### `print({ comments?: string, pragmas?: {[key: string]: string | string[]} }): string`
|
|
|
|
Prints an object of key-value pairs back into a docblock. If `comments` are provided, they will be positioned on the top of the docblock.
|