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>
eslint-plugin-promise
Enforce best practices for JavaScript promises.
Installation
You'll first need to install ESLint:
npm install eslint --save-dev
Next, install eslint-plugin-promise:
npm install eslint-plugin-promise --save-dev
Note: If you installed ESLint globally (using the -g flag) then you must
also install eslint-plugin-promise globally.
Usage
Add promise to the plugins section of your .eslintrc.json configuration
file. You can omit the eslint-plugin- prefix:
{
"plugins": ["promise"]
}
Then configure the rules you want to use under the rules section.
{
"rules": {
"promise/always-return": "error",
"promise/no-return-wrap": "error",
"promise/param-names": "error",
"promise/catch-or-return": "error",
"promise/no-native": "off",
"promise/no-nesting": "warn",
"promise/no-promise-in-callback": "warn",
"promise/no-callback-in-promise": "warn",
"promise/avoid-new": "warn",
"promise/no-new-statics": "error",
"promise/no-return-in-finally": "warn",
"promise/valid-params": "warn",
"promise/no-multiple-resolved": "error"
}
}
or start with the recommended rule set:
-
eslint.config.js:import pluginPromise from 'eslint-plugin-promise' export default [ // ... pluginPromise.configs['flat/recommended'], ] -
.eslintrc.*:{ "extends": ["plugin:promise/recommended"] }
Rules
💼 Configurations enabled in.
⚠️ Configurations set to warn in.
🚫 Configurations disabled in.
✅ Set in the flat/recommended configuration.
✅ Set in the recommended configuration.
🔧 Automatically fixable by the --fix CLI option.
| Name | Description | 💼 | ⚠️ | 🚫 | 🔧 |
|---|---|---|---|---|---|
| always-return | Require returning inside each then() to create readable and reusable Promise chains. |
✅ | |||
| avoid-new | Disallow creating new promises outside of utility libs (use pify instead). |
✅ | |||
| catch-or-return | Enforce the use of catch() on un-returned promises. |
✅ | |||
| no-callback-in-promise | Disallow calling cb() inside of a then() (use nodeify instead). |
✅ | |||
| no-multiple-resolved | Disallow creating new promises with paths that resolve multiple times. | ||||
| no-native | Require creating a Promise constructor before using it in an ES5 environment. |
✅ | |||
| no-nesting | Disallow nested then() or catch() statements. |
✅ | |||
| no-new-statics | Disallow calling new on a Promise static method. |
✅ | 🔧 | ||
| no-promise-in-callback | Disallow using promises inside of callbacks. | ✅ | |||
| no-return-in-finally | Disallow return statements in finally(). |
✅ | |||
| no-return-wrap | Disallow wrapping values in Promise.resolve or Promise.reject when not needed. |
✅ | |||
| param-names | Enforce consistent param names and ordering when creating new promises. | ✅ | |||
| prefer-await-to-callbacks | Prefer async/await to the callback pattern. |
||||
| prefer-await-to-then | Prefer await to then()/catch()/finally() for reading Promise values. |
||||
| valid-params | Enforces the proper number of arguments are passed to Promise functions. | ✅ |
Maintainers
- Jamund Ferguson - @xjamundx
- Macklin Underdown - @macklinu
- Aadit M Shah - @aaditmshah
License
- (c) MMXV jden mailto:jason@denizac.org - ISC license.
- (c) 2016 Jamund Ferguson mailto:jamund@gmail.com - ISC license.