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>
66 lines
2.3 KiB
Markdown
66 lines
2.3 KiB
Markdown
[type-definitions]: https://github.com/jestjs/jest/blob/main/packages/jest-types/src/Circus.ts
|
|
|
|
<h1 align="center">
|
|
<img src="https://jestjs.io/img/jest.png" height="150" width="150"/>
|
|
<img src="https://jestjs.io/img/circus.png" height="150" width="150"/>
|
|
<p align="center">jest-circus</p>
|
|
<p align="center">The next-gen test runner for Jest</p>
|
|
</h1>
|
|
|
|
## Overview
|
|
|
|
Circus is a flux-based test runner for Jest that is fast, maintainable, and simple to extend.
|
|
|
|
Circus allows you to bind to events via an optional event handler on any [custom environment](https://jestjs.io/docs/configuration#testenvironment-string). See the [type definitions][type-definitions] for more information on the events and state data currently available.
|
|
|
|
```js
|
|
import {Event, State} from 'jest-circus';
|
|
import {TestEnvironment as NodeEnvironment} from 'jest-environment-node';
|
|
|
|
class MyCustomEnvironment extends NodeEnvironment {
|
|
//...
|
|
|
|
async handleTestEvent(event: Event, state: State) {
|
|
if (event.name === 'test_start') {
|
|
// ...
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
Mutating event or state data is currently unsupported and may cause unexpected behavior or break in a future release without warning. New events, event data, and/or state data will not be considered a breaking change and may be added in any minor release.
|
|
|
|
Note, that `jest-circus` test runner would pause until a promise returned from `handleTestEvent` gets fulfilled. **However, there are a few events that do not conform to this rule, namely**: `start_describe_definition`, `finish_describe_definition`, `add_hook`, `add_test` or `error` (for the up-to-date list you can look at [SyncEvent type in the types definitions][type-definitions]). That is caused by backward compatibility reasons and `process.on('unhandledRejection', callback)` signature, but that usually should not be a problem for most of the use cases.
|
|
|
|
## Installation
|
|
|
|
> Note: As of Jest 27, `jest-circus` is the default test runner, so you do not have to install it to use it.
|
|
|
|
Install `jest-circus` using yarn:
|
|
|
|
```bash
|
|
yarn add --dev jest-circus
|
|
```
|
|
|
|
Or via npm:
|
|
|
|
```bash
|
|
npm install --save-dev jest-circus
|
|
```
|
|
|
|
## Configure
|
|
|
|
Configure Jest to use `jest-circus` via the [`testRunner`](https://jestjs.io/docs/configuration#testrunner-string) option:
|
|
|
|
```json
|
|
{
|
|
"testRunner": "jest-circus/runner"
|
|
}
|
|
```
|
|
|
|
Or via CLI:
|
|
|
|
```bash
|
|
jest --testRunner='jest-circus/runner'
|
|
```
|