hana-developer-cli-tool-example: Instructions file for GitHub Copilot

.github/instructions/testing.instructions.md

hana-developer-cli-tool-example testing.instructions.md is an instructions file for GitHub Copilot from SAP-samples/hana-developer-cli-tool-example. It costs 3,615 tokens per session, scanned A, original, Apache-2.0.

Project-specific guidance for testing CLI commands, helper code, web routes, and error cases using Mocha, a JavaScript test runner.

In plain words
What is it for?
Use it when creating or updating unit, integration, command-line, flag-validation, or error-handling tests.
Why use it?
It provides consistent test structure, assertions, isolation, command-line checks, and validation of failures so changes are less likely to cause regressions.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is SAP-samples/hana-developer-cli-tool-example's own configuration. It tells GitHub Copilot how to work on hana-developer-cli-tool-example itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hana-developer-cli-tool-example configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { assert } from '../base.js'.

Reuse

Borrowing it

Nothing to install: this file belongs to SAP-samples/hana-developer-cli-tool-example. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/testing.instructions.md
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for hana-developer-cli-tool-example testing.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/testing/github.svg)](https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/testing)
Your own site
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/testing"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hana-developer-cli-tool-example testing.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/testing"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,615 This file is loaded in full into every session.
When invoked 3,615 The same file — it is already loaded in full.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.03615 $0.03615
Opus 5.5 $0.01446 $0.01446
Sonnet 5.5 $0.00723 $0.00723
Haiku 4.5 $0.00362 $0.00362

Measured 1mo ago against content hash 93b54e210123, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hana-developer-cli-tool-example testing.instructions.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

child_process.exec('node bin/command.js --limit -5 --quiet',
.github/instructions/testing.instructions.md · 531 lines

How it starts

The opening of the file, as written. The whole thing — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Guidelines

Use this guide when creating or updating test files for this project. Tests validate CLI commands, utilities, routes, and error handling to ensure reliability and prevent regressions.

Scope and Test Types

This project contains multiple test types:

  1. CLI Command Tests - Validate bin/*.js commands via subprocess execution
  2. Unit Tests - Test individual utility functions in isolation
  3. Integration Tests - Test routes and Express app functionality using appFactory
  4. Error Handling Tests - Validate graceful error scenarios and edge cases
  5. Flag Validation Tests - Verify command-line argument parsing and constraints

Test Framework and Configuration

  • Test Runner: Mocha (@latest)
  • Assertion Library: Node.js built-in assert module
  • Reporting: mochawesome for HTML reports
  • Execution: Parallel (16 jobs) via .mocharc.json
  • Coverage Tool: mochawesome with context injection
  • Timeout: Default 10 seconds (set per describe/it block as needed)

Configuration file: .mocharc.json

{
    "timeout": "10s",
    "parallel": true,
    "jobs": 16,
    "reporter": "spec",
    "exit": true,
    "require": ["./tests/helper.js"]
}

File Naming and Organization

  • Naming: Use FileName.Test.js or fileName.test.js pattern (flexible casing + .Test.js or .test.js suffix)
  • Location: Tests live in tests/ directory, mirroring source structure
  • Grouping: Organize related tests in subdirectories:
    • tests/ - CLI command tests
    • tests/utils/ - Utility function tests
    • tests/routes/ - Route integration tests

Examples:

  • CLI command: tests/tables.Test.js (tests bin/tables.js)
  • Utility test: tests/utils/base.Test.js
  • Route test: tests/routes/api.test.js
  • Utility helper: tests/utils/connections.Test.js

Test Structure Template

CLI Command Tests

CLI tests execute commands via subprocess and validate output:

// @ts-check
/**
 * @module commandName - Tests for bin/commandName.js
 * 
 * Validates command-line execution, flag parsing, help output,
 * and integration with the CLI framework.
 */

import * as base from './base.js'

describe('commandName', function () {

    it("returns help output", function (done) {
        const localTest = base.myTest.bind(this)
        localTest("node bin/commandName.js --help", done)
    })

    it("returns normal output", function (done) {
        const localTest = base.myTest.bind(this)
        localTest("node bin/commandName.js --quiet", done)
    })

    it("accepts and uses limit flag", function (done) {
        const localTest = base.myTest.bind(this)
        localTest("node bin/commandName.js --limit 10 --quiet", done)
    })

})

Read the full file on GitHub · 531 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 531 lines · 3,615 tokens per session scan A 93b54e210123

Subscribe to this mod's changes

hana-developer-cli-tool-example testing.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (114 stars, last pushed 11d ago), licensed Apache-2.0. It adds 3,615 tokens to every session, about $0.0145 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,549 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens