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>
70 lines
2.4 KiB
Markdown
70 lines
2.4 KiB
Markdown
agent-base
|
|
==========
|
|
### Turn a function into an [`http.Agent`][http.Agent] instance
|
|
|
|
This module is a thin wrapper around the base `http.Agent` class.
|
|
|
|
It provides an abstract class that must define a `connect()` function,
|
|
which is responsible for creating the underlying socket that the HTTP
|
|
client requests will use.
|
|
|
|
The `connect()` function may return an arbitrary `Duplex` stream, or
|
|
another `http.Agent` instance to delegate the request to, and may be
|
|
asynchronous (by defining an `async` function).
|
|
|
|
Instances of this agent can be used with the `http` and `https`
|
|
modules. To differentiate, the options parameter in the `connect()`
|
|
function includes a `secureEndpoint` property, which can be checked
|
|
to determine what type of socket should be returned.
|
|
|
|
#### Some subclasses:
|
|
|
|
Here are some more interesting uses of `agent-base`.
|
|
Send a pull request to list yours!
|
|
|
|
* [`http-proxy-agent`][http-proxy-agent]: An HTTP(s) proxy `http.Agent` implementation for HTTP endpoints
|
|
* [`https-proxy-agent`][https-proxy-agent]: An HTTP(s) proxy `http.Agent` implementation for HTTPS endpoints
|
|
* [`pac-proxy-agent`][pac-proxy-agent]: A PAC file proxy `http.Agent` implementation for HTTP and HTTPS
|
|
* [`socks-proxy-agent`][socks-proxy-agent]: A SOCKS proxy `http.Agent` implementation for HTTP and HTTPS
|
|
|
|
Example
|
|
-------
|
|
|
|
Here's a minimal example that creates a new `net.Socket` or `tls.Socket`
|
|
based on the `secureEndpoint` property. This agent can be used with both
|
|
the `http` and `https` modules.
|
|
|
|
```ts
|
|
import * as net from 'net';
|
|
import * as tls from 'tls';
|
|
import * as http from 'http';
|
|
import { Agent } from 'agent-base';
|
|
|
|
class MyAgent extends Agent {
|
|
connect(req, opts) {
|
|
// `secureEndpoint` is true when using the "https" module
|
|
if (opts.secureEndpoint) {
|
|
return tls.connect(opts);
|
|
} else {
|
|
return net.connect(opts);
|
|
}
|
|
}
|
|
});
|
|
|
|
// Keep alive enabled means that `connect()` will only be
|
|
// invoked when a new connection needs to be created
|
|
const agent = new MyAgent({ keepAlive: true });
|
|
|
|
// Pass the `agent` option when creating the HTTP request
|
|
http.get('http://nodejs.org/api/', { agent }, (res) => {
|
|
console.log('"response" event!', res.headers);
|
|
res.pipe(process.stdout);
|
|
});
|
|
```
|
|
|
|
[http-proxy-agent]: ../http-proxy-agent
|
|
[https-proxy-agent]: ../https-proxy-agent
|
|
[pac-proxy-agent]: ../pac-proxy-agent
|
|
[socks-proxy-agent]: ../socks-proxy-agent
|
|
[http.Agent]: https://nodejs.org/api/http.html#http_class_http_agent
|