agentsclimarketplace

Run tests

Skill bg-szy/TOP-SKILLS/skills/marketplace/run-tests

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install
npx -y skills add bg-szy/TOP-SKILLS --skill run-tests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run unit and integration tests for Catalyst-Relay. Use when asked to test, run tests, verify changes, or check if code works.

SKILL.md

2.5 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

Running Tests

When to Use

  • User asks to run tests or verify changes
  • After implementing a feature or fix
  • Before committing or publishing

Unit Tests

bun test                      # All tests
bun test --watch              # Watch mode
bun test src/__tests__/core   # Specific directory

Node.js Compatibility Check

Before publishing, verify library imports work in Node:

node --experimental-strip-types -e "import('.')"

Integration Tests

Integration tests require SAP credentials and connect to a live SAP system.

Credentials

There are two ways credentials can be provided:

  1. OS Keyring (recommended): If SAP_TEST_SYSTEM_ALIAS is set in .env (e.g. TKO-DS4), the test helpers automatically read the password from the OS keyring where Catalyst-CLI stores it. No manual password entry needed.
  2. Environment variable: SAP_PASSWORD can be set directly or passed to ./test.bat <password>.

The keyring lookup uses the Catalyst-CLI service name and key format ({alias}:basic:password). If both are available, SAP_PASSWORD takes priority.

Workflow

  1. Confirm .env exists with system connection details (URL, client, username)
  2. Run bun test (credentials resolve from keyring) or ./test.bat <SAP_PASSWORD>
  3. Read test.output for integration test results if using test.bat

Environment Variables

VariableRequiredDescription
SAP_TEST_ADT_URLYesSAP ADT server URL
SAP_TEST_CLIENTYesSAP client number
SAP_TEST_USERNAMEYesSAP username
SAP_TEST_SYSTEM_ALIASNoSystem alias for keyring credential lookup
SAP_PASSWORDNo*SAP password (not needed if keyring is configured)
SAP_TEST_PACKAGENoTarget package (default: $TMP)
SAP_TEST_TRANSPORTNoTransport request

See .env.templ for a template.

Test Coverage Map

Test FileCoverage
cds-workflow.test.tsCDS View + Access Control lifecycle
abap-class-workflow.test.tsABAP Class CRAUD
abap-program-workflow.test.tsABAP Program CRAUD
table-workflow.test.tsTable + data preview
discovery-workflow.test.tsPackages, tree, transports
search-workflow.test.tsSearch + where-used
data-preview-workflow.test.tsPreview on T000 table
upsert-workflow.test.tsCreate vs update detection

What ships with it: 1 file

34.4 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.