test-add

Test-Add — Universal Test Scaffold

Create a structured test definition (meta.yaml) and test file for any source file.

When to Use

• User types /test-add {file-path}
• User says "add tests for {file}", "테스트 추가"

Instructions

Step 1: Validate Target

Read the file at the given path. If it doesn't exist, report and stop.

Detect the programming language from the file extension:

• .ts, .tsx → TypeScript (framework: vitest)
• .js, .jsx → JavaScript (framework: vitest)
• .py → Python (framework: pytest)
• .go → Go (framework: go test)
• .rs → Rust (framework: cargo test)
• .rb → Ruby (framework: rspec)
• Other → ask user which framework to use

Step 2: Analyze the File

Read the source file. Identify:

• Exported functions, classes, methods
• Input parameters and return types
• Edge cases (null handling, error paths, boundary values)
• Dependencies and side effects (DB, API, filesystem)

Step 3: Create Test Directory

Mirror the source path under .omniscitus/tests/:

mkdir -p .omniscitus/tests/{path-to-source-dir}

Example: src/lib/auth.ts → .omniscitus/tests/src/lib/auth/

Step 4: Generate meta.yaml

Create .omniscitus/tests/{path}/meta.yaml.

CRITICAL: Each suite MUST include a signature block with typed params and returns. This enables type-safe test case creation in the Birdview UI.

target: {relative-path-to-source}
language: {detected-language}
framework: {detected-framework}
last_updated: {YYYY-MM-DD}

suites:
  - name: {function-or-class-name}
    type: unittest               # unittest | integration | e2e
    signature:
      params:
        - name: {param-name}
          type: string           # string | number | boolean | object | array
        - name: {param-name}
          type: object
          optional: true         # mark optional params
          properties:
            {prop}: {type}       # nested object shape
      returns:
        type: object             # return type
        properties:
          {prop}: {type}         # return shape for objects
    cases:
      - title: "{descriptive test name}"
        description: "{what this test verifies}"
        input:
          {param}: {value}
        expected:
          strategy: exact          # exact | contains | schema | regex
          value: {expected-output}