Agent skill

Chatqna Run Unit Tests

by open-edge-platform in open-edge-platform/edge-ai-libraries

Run ChatQnA Core unit tests for backend (pytest via uv) and frontend UI (vitest), including runtime selection (openvino or ollama), coverage options, and concise pass/fail evidence.

Apache-2.0Auto-check passedTesting & QA

Install Chatqna Run Unit Tests

skills CLI
$ npx skills add open-edge-platform/edge-ai-libraries --skill chatqna-run-unit-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install open-edge-platform/edge-ai-libraries chatqna-run-unit-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/open-edge-platform/edge-ai-libraries.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sample-applications/chat-question-and-answer-core/.github/skills/chatqna-run-unit-tests .claude/skills/chatqna-run-unit-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chatqna-run-unit-tests
GitHub stars
169
Token cost
~1.4k tokens
SKILL.md length
554 words
Files
5 (incl. scripts)
Skills in repo
29
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run ChatQnA Core unit tests for backend (pytest via uv) and frontend UI (vitest), including runtime selection (openvino or ollama), coverage options, and concise pass/fail evidence.

  • Works in 4 steps: Preflight → Backend Unit Tests → Frontend UI Unit Tests → …
  • The user says run unit tests
  • SKILL.md covers Environment setup (run first), What This Skill Produces, When to Use and Inputs To Confirm, plus 4 more sections
  • Runs Shell scripts from its folder; calls uv, npm and bash

What it does

Chatqna Run Unit Tests is an agent skill from open-edge-platform/edge-ai-libraries. Run ChatQnA Core unit tests for backend (pytest via uv) and frontend UI (vitest), including runtime selection (openvino or ollama), coverage options, and concise pass/fail evidence. Use this skill when the user says "run unit tests", "run backend tests", "run UI tests", "pytest", or "vitest".

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `benchmark/benchmark.md`, `evals/evals.json` and `evals/trigger-evals.json`).

It sits in Testing & QA, covering Unit testing. It works with pytest, Vitest and Ollama. The repository describes itself as: Libraries, microservices, tools, and other reference software, supporting development of performance-optimized Edge AI applications. The licence is Apache-2.0.

When your agent uses it

  • The user says run unit tests
  • Run backend tests

Example prompts

  • “run unit tests”
  • “run backend tests”
  • “run UI tests”
  • “/chatqna-run-unit-tests”

Requirements

  • Python 3
  • Node.js
  • A Bash shell

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Preflight
  2. Backend Unit Tests
  3. Frontend UI Unit Tests
  4. Optional Targeted Test Runs

What it can do on your machine

Read from SKILL.md and the folder at commit cdf860c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • uv
    • npm
    • bash
    • python3
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Chatqna Run Unit Tests loads about 1.4k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 554 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from open-edge-platform/edge-ai-libraries at commit cdf860c, republished under its Apache-2.0 licence (© open-edge-platform). 554 words, ~1,382 tokens.

Download SKILL.mdSave it as .claude/skills/chatqna-run-unit-tests/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
chatqna-run-unit-tests
description
Run ChatQnA Core unit tests for backend (pytest via uv) and frontend UI (vitest), including runtime selection (openvino or ollama), coverage options, and concise pass/fail evidence. Use this skill when the user says "run unit tests", "run backend tests", "run UI tests", "pytest", or "vitest".
license
Apache-2.0
metadata.version
1.0.0
metadata.tags
chatqna tests unit-tests pytest vitest backend frontend openvino ollama
<!--
SPDX-FileCopyrightText: (C) 2026 Intel Corporation
SPDX-License-Identifier: Apache-2.0
-->

ChatQnA Run Unit Tests

Run unit tests for Chat Question-and-Answer Core backend and frontend UI using the repository-supported commands.

Environment setup (run first)

This skill operates on real ChatQnA source files, so the ChatQnA application must be present and commands must run from the app root. Do this before any test workflow, whether or not source is already in your workspace.

Run the bundled bootstrap. It searches for an existing ChatQnA checkout by walking up from the current directory and checking the enclosing git repo, then reuses it without re-cloning. Only when no checkout is found does it do a shallow, single-branch, sparse checkout of just sample-applications/chat-question-and-answer-core from main.

It prints the resolved app root on stdout:

bash
# SKILL_DIR is this skill directory. In-repo it is:
# .github/skills/chatqna-run-unit-tests
SKILL_DIR=".github/skills/chatqna-run-unit-tests"
APP_ROOT="$(bash "$SKILL_DIR/scripts/chatqna-bootstrap.sh")"
cd "$APP_ROOT"

Every command below assumes the working directory is this APP_ROOT.

To use a fork/branch or a specific clone path, override these before running the bootstrap script:

  • CHATQNA_REPO_URL
  • CHATQNA_REPO_BRANCH
  • CHATQNA_CLONE_DIR
  • CHATQNA_FORCE_CLONE (set to 1 to force clone)

Codebase root: sample-applications/chat-question-and-answer-core/

What This Skill Produces

  • Executed unit tests for one or both scopes:
    • Backend (pytest via uv run)
    • Frontend UI (vitest via npm run)
  • Optional coverage execution for backend and UI.
  • A concise test report containing:
    • scope executed (backend/ui/both)
    • runtime used for backend (openvino or ollama)
    • pass/fail status and failing test identifiers
    • exact command(s) run as evidence

When to Use

  • After user-visible application code changes in backend or UI, run unit tests by default to validate regressions.
  • Treat unit-test execution as the default post-change validation step unless the user explicitly says not to run tests.
  • Skip unit-test execution only when the user clearly opts out (for example: "do not run tests", "skip unit tests", "no tests needed").
  • "Run unit tests"
  • "Run backend tests"
  • "Run UI tests"
  • "Run pytest"
  • "Run vitest"
  • "Run test coverage"

Inputs To Confirm

Before running commands, confirm or infer:

  1. Scope: backend, ui, or both (default: both)
  2. Backend runtime: openvino or ollama (default: openvino)
  3. Coverage mode: on or off (default: off)
  4. Optional target narrowing (single file or test pattern)

If the user asks for "all unit tests", run backend + UI.

Show full SKILL.md (213 more words)Show less

Decision Logic

  • If scope is backend:
    • run backend test workflow only
  • If scope is ui:
    • run UI test workflow only
  • If scope is both:
    • run backend workflow first, then UI workflow
  • If backend runtime is not provided:
    • default to openvino
  • If coverage is requested:
    • backend: add --cov=app --cov-report=term-missing
    • UI: use npm run coverage

Workflow

Run from sample-applications/chat-question-and-answer-core.

1. Preflight
bash
python3 --version
uv --version
node --version
npm --version
2. Backend Unit Tests

Install/sync dependencies if needed:

bash
uv sync --all-groups

Run backend tests by runtime:

bash
# OpenVINO backend tests (default)
uv run pytest --model-runtime=openvino

# Ollama backend tests
uv run pytest --model-runtime=ollama

Backend coverage mode:

bash
# OpenVINO coverage
uv run pytest --model-runtime=openvino --cov=app --cov-report=term-missing

# Ollama coverage
uv run pytest --model-runtime=ollama --cov=app --cov-report=term-missing
3. Frontend UI Unit Tests

Switch to UI directory and install deps if needed:

bash
cd ui
npm install

Run UI tests:

bash
npm run test

UI coverage mode:

bash
npm run coverage

Optional interactive runner (only when explicitly requested):

bash
npm run test:ui
4. Optional Targeted Test Runs

Backend single file:

bash
uv run pytest tests/test_server.py --model-runtime=openvino

UI targeted pattern example:

bash
cd ui
npm run test -- Conversation

Failure Handling

  • uv not installed:
    • install uv and re-run sync/tests
  • Backend dependency or import failures:
    • run uv sync --all-groups and retry
  • npm or node_modules issues:
    • run npm install in ui/ and retry
  • Runtime mismatch for backend tests:
    • re-run with explicit --model-runtime=openvino|ollama
  • Failing tests:
    • report failing test names and first actionable traceback lines

Completion Criteria

  1. Requested test scope (backend/ui/both) is executed.
  2. For backend, runtime selection is explicit (openvino or ollama).
  3. If coverage requested, coverage command(s) are run.
  4. Response includes exact commands and pass/fail evidence.
  5. If failures occur, response includes failing tests and next actionable step.

© open-edge-platform, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts) in sample-applications/chat-question-and-answer-core/.github/skills/chatqna-run-unit-tests of open-edge-platform/edge-ai-libraries.

  • SKILL.md
  • benchmark/benchmark.md
  • evals/evals.json
  • evals/trigger-evals.json
  • scripts/chatqna-bootstrap.sh

Open the folder on GitHubat commit cdf860c

Compare with similar skills

Chatqna Run Unit Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Chatqna Run Unit Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chatqna Run Unit Tests this skillopen-edge-platform/edge-ai-libraries169—~1.4kAutomated safety check: PassApache-2.0
Test GuardamElnagdy/guard-skills1.3k2 repos~2.1kAutomated safety check: PassMIT
Designing TestsCloudAI-X/claude-workflow-v21.4k1 repos~1.5kAutomated safety check: PassMIT
Run Testsartcc/freelingo162—~976Automated safety check: PassAGPL-3.0
MoAI TDD Workflowmodu-ai/moai-adk1.2k—~3.1kAutomated safety check: PassApache-2.0
Test-Driven Development Enforcerzereight/gitlab-mcp2k1 repos~904Automated safety check: PassMIT

Similar skills

  • Test Guard

    amElnagdy/guard-skills

    Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.

    1.3k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed
  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-check passed
  • Run Tests

    artcc/freelingo

    A skill your agent uses when the user asks to run tests, ejecutar tests, lanzar tests, pytest, vitest, check types, typecheck, lint, or verify the codebase.

    162 GitHub stars~976 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • MoAI TDD Workflow

    modu-ai/moai-adk

    Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.

    1.2k GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Enforces strict red-green-refactor, with a failing test first, the minimum code to pass it, then cleanup, and a quick reference for common test runners.

    2k GitHub starsUsed in 1 repo~904 tokens
    Testing & QAAuto-check passed
  • Testing Livekit Agents

    livekit-examples/agent-starter-python

    Writes turn-level tests for a LiveKit agent in the user's normal test suite: pytest (Python) or Vitest (Node.js).

    264 GitHub starsUsed in 1 repo~1.9k tokens
    Testing & QAAuto-check passed

More from open-edge-platform/edge-ai-libraries

All 29 skills in this repo
  • Time Series Analytics User

    open-edge-platform/edge-ai-libraries

    Build a new time-series analytics use case on top of the deployed Time Series Analytics microservice — bring it up with Docker Compose (from a repo clone, or by fetching the compose files from…

    169 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Vss Add Nest Module

    open-edge-platform/edge-ai-libraries

    Scaffolds and wires a new NestJS service/module for the Video Search & Summarization sample app's pipeline-manager using the repo's real conventions.

    169 GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Chatqna Helm Deploy

    open-edge-platform/edge-ai-libraries

    Deploy Chat Question-and-Answer Core to Kubernetes using Helm (OpenVINO CPU, OpenVINO GPU, or Ollama), including values.yaml configuration, helm install/upgrade, deployment verification, uninstall…

    169 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Generate Changelog

    open-edge-platform/edge-ai-libraries

    Generates or updates CHANGELOG.md by analyzing git commit history between two branches, tags, or revisions in ANY git repository or folder.

    169 GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Vss Deploy

    open-edge-platform/edge-ai-libraries

    Deploys and manages VSS through setup.sh and its Docker Compose overlays.

    169 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Vss Deploy Helm

    open-edge-platform/edge-ai-libraries

    A skill your agent uses whenever a developer needs to deploy VSS to Kubernetes, helm install VSS, configure values.yaml for VSS, or run VSS on k8s with GPU/vLLM for the…

    169 GitHub stars~3.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Chatqna Run Unit Tests

What does Chatqna Run Unit Tests do?

Run ChatQnA Core unit tests for backend (pytest via uv) and frontend UI (vitest), including runtime selection (openvino or ollama), coverage options, and concise pass/fail evidence. Chatqna Run Unit Tests is an agent skill from open-edge-platform/edge-ai-libraries. Run ChatQnA Core unit tests for backend (pytest via uv) and frontend UI (vitest), including runtime selection (openvino or ollama), coverage options, and concise pass/fail evidence.

When should I use Chatqna Run Unit Tests?

Chatqna Run Unit Tests fits situations like: the user says run unit tests; run backend tests.

How do I install Chatqna Run Unit Tests in Claude Code?

Run `npx skills add open-edge-platform/edge-ai-libraries --skill chatqna-run-unit-tests -a claude-code`. Or copy the skill folder (sample-applications/chat-question-and-answer-core/.github/skills/chatqna-run-unit-tests in open-edge-platform/edge-ai-libraries) into .claude/skills/chatqna-run-unit-tests in your project. Claude Code loads it when a task matches its description.

How do I install Chatqna Run Unit Tests in Codex?

Run `npx skills add open-edge-platform/edge-ai-libraries --skill chatqna-run-unit-tests -a codex`. Or copy the skill folder (sample-applications/chat-question-and-answer-core/.github/skills/chatqna-run-unit-tests in open-edge-platform/edge-ai-libraries) into .agents/skills/chatqna-run-unit-tests in your project. Codex loads it when a task matches its description.

Can I use Chatqna Run Unit Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add open-edge-platform/edge-ai-libraries --skill chatqna-run-unit-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chatqna-run-unit-tests, .gemini/skills/chatqna-run-unit-tests, .github/skills/chatqna-run-unit-tests and .opencode/skills/chatqna-run-unit-tests in your project.

What does Chatqna Run Unit Tests need to run?

Going by SKILL.md and its folder, Chatqna Run Unit Tests needs a shell for the scripts in its folder and the command-line tools its instructions call (uv, npm, bash, python3 and node). Our summary lists: Python 3; Node.js; A Bash shell.

Does Chatqna Run Unit Tests access the network?

SKILL.md contains no URLs. Its commands use uv and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Chatqna Run Unit Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Chatqna Run Unit Tests use?

Chatqna Run Unit Tests is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chatqna Run Unit Tests use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Chatqna Run Unit Tests?

Skills that share tags, products or a category with Chatqna Run Unit Tests: Test Guard (amElnagdy/guard-skills, 1.3k stars), Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars), Run Tests (artcc/freelingo, 162 stars) and MoAI TDD Workflow (modu-ai/moai-adk, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chatqna Run Unit Tests?

open-edge-platform (a GitHub organization) maintains it in open-edge-platform/edge-ai-libraries, which has 169 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 9, 2026.

Source: open-edge-platform/edge-ai-libraries on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.