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>
ci-info
Get details about the current Continuous Integration environment.
Please open an issue if your CI server isn't properly detected :)
Installation
npm install ci-info --save
Usage
var ci = require('ci-info')
if (ci.isCI) {
console.log('The name of the CI server is:', ci.name)
} else {
console.log('This program is not running on a CI server')
}
Supported CI tools
Officially supported CI servers:
| Name | Constant | isPR |
|---|---|---|
| AWS CodeBuild | ci.CODEBUILD |
🚫 |
| AppVeyor | ci.APPVEYOR |
✅ |
| Azure Pipelines | ci.AZURE_PIPELINES |
✅ |
| Appcircle | ci.APPCIRCLE |
🚫 |
| Bamboo by Atlassian | ci.BAMBOO |
🚫 |
| Bitbucket Pipelines | ci.BITBUCKET |
✅ |
| Bitrise | ci.BITRISE |
✅ |
| Buddy | ci.BUDDY |
✅ |
| Buildkite | ci.BUILDKITE |
✅ |
| CircleCI | ci.CIRCLE |
✅ |
| Cirrus CI | ci.CIRRUS |
✅ |
| Codefresh | ci.CODEFRESH |
✅ |
| Codeship | ci.CODESHIP |
🚫 |
| Drone | ci.DRONE |
✅ |
| dsari | ci.DSARI |
🚫 |
| Expo Application Services | ci.EAS |
🚫 |
| Gerrit CI | ci.GERRIT |
🚫 |
| GitHub Actions | ci.GITHUB_ACTIONS |
✅ |
| GitLab CI | ci.GITLAB |
✅ |
| GoCD | ci.GOCD |
🚫 |
| Google Cloud Build | ci.GOOGLE_CLOUD_BUILD |
🚫 |
| Harness CI | ci.HARNESS |
🚫 |
| Heroku | ci.HEROKU |
🚫 |
| Hudson | ci.HUDSON |
🚫 |
| Jenkins CI | ci.JENKINS |
✅ |
| LayerCI | ci.LAYERCI |
✅ |
| Magnum CI | ci.MAGNUM |
🚫 |
| Netlify CI | ci.NETLIFY |
✅ |
| Nevercode | ci.NEVERCODE |
✅ |
| ReleaseHub | ci.RELEASEHUB |
🚫 |
| Render | ci.RENDER |
✅ |
| Sail CI | ci.SAIL |
✅ |
| Screwdriver | ci.SCREWDRIVER |
✅ |
| Semaphore | ci.SEMAPHORE |
✅ |
| Shippable | ci.SHIPPABLE |
✅ |
| Solano CI | ci.SOLANO |
✅ |
| Sourcehut | ci.SOURCEHUT |
🚫 |
| Strider CD | ci.STRIDER |
🚫 |
| TaskCluster | ci.TASKCLUSTER |
🚫 |
| TeamCity by JetBrains | ci.TEAMCITY |
🚫 |
| Travis CI | ci.TRAVIS |
✅ |
| Vercel | ci.VERCEL |
✅ |
| Visual Studio App Center | ci.APPCENTER |
🚫 |
| Woodpecker | ci.WOODPECKER |
✅ |
API
ci.name
Returns a string containing name of the CI server the code is running on.
If CI server is not detected, it returns null.
Don't depend on the value of this string not to change for a specific
vendor. If you find your self writing ci.name === 'Travis CI', you
most likely want to use ci.TRAVIS instead.
ci.isCI
Returns a boolean. Will be true if the code is running on a CI server,
otherwise false.
Some CI servers not listed here might still trigger the ci.isCI
boolean to be set to true if they use certain vendor neutral
environment variables. In those cases ci.name will be null and no
vendor specific boolean will be set to true.
ci.isPR
Returns a boolean if PR detection is supported for the current CI server. Will
be true if a PR is being tested, otherwise false. If PR detection is
not supported for the current CI server, the value will be null.
ci.<VENDOR-CONSTANT>
A vendor specific boolean constant is exposed for each support CI
vendor. A constant will be true if the code is determined to run on
the given CI server, otherwise false.
Examples of vendor constants are ci.TRAVIS or ci.APPVEYOR. For a
complete list, see the support table above.
Deprecated vendor constants that will be removed in the next major release:
ci.TDDIUM(Solano CI) This have been renamedci.SOLANO
Ports
ci-info has been ported to the following languages
| Language | Repository |
|---|---|
| Go | https://github.com/hofstadter-io/cinful |
| Rust | https://github.com/sagiegurari/ci_info |
| Kotlin | https://github.com/cloudflightio/ci-info |