test

Run ClickHouse stateless or integration tests from the repository.

49.1k|8.8k|Updated Jun 2, 2016
One-click install
npx skills add https://github.com/ClickHouse/ClickHouse --skill test-clickhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/ClickHouse/ClickHouse/tree/main/.claude/skills/test
Command: npx skills add https://github.com/ClickHouse/ClickHouse --skill test-clickhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines running ClickHouse tests (stateless and integration) directly from the repository, ensuring consistent results and faster feedback.

Core Features & Use Cases

  • Test discovery: Run stateless tests from tests/queries/0_stateless/ and integration tests from tests/integration/.
  • Flexible selection: Specify a test name or let the skill auto-detect the type based on naming and location.
  • Managed execution: Logs are written to a temporary file, and results are analyzed by Task tooling; tests run in the background to free up your time.
  • Environment awareness: Stateless tests run from the repository root using the configured build directory; integration tests leverage Docker containers via Praktika.

Quick Start

From the repository root, invoke the skill with a test name, e.g. /test test_keeper_three_nodes_start or /test 03312_issue_63093. The system will guide you through choosing stateless or integration tests and will stream logs in real time.

Frequently Asked Questions about test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run ClickHouse stateless and integration tests from the repository?

To run ClickHouse tests, invoke the skill with a test name like /test 03312_issue_63093. Stateless tests execute from the repository root using the configured build directory, while integration tests run via Docker containers managed by praktika.

How does auto-detection work when selecting a ClickHouse test to run?

Auto-detection for ClickHouse tests selects the test type based on the provided naming convention and location. You can specify a test name directly, and the system determines whether to run it as a stateless or integration test automatically.

Do I need Docker to run ClickHouse integration tests?

Yes, Docker is required for ClickHouse integration tests. Integration tests leverage Docker containers managed by praktika, whereas stateless tests run directly from the repository root using the configured build directory without Docker.

What is the best way to execute long-running ClickHouse tests without blocking my terminal?

The best way to execute long-running ClickHouse tests is through the skill's managed background execution. Tests run in the background to free up your time, with logs written to a temporary file and results analyzed by Task tooling while streaming logs in real time.

Where does the test runner discover stateless and integration tests in the ClickHouse project?

Test discovery locates ClickHouse stateless tests in the tests/queries/0_stateless/ directory and integration tests in the tests/integration/ directory. The runner automatically identifies and executes the requested tests from these specific repository locations.

Can I view real-time logs when running ClickHouse tests in the background?

Yes, you can view real-time logs when running ClickHouse tests in the background. The skill streams logs in real time while writing them to a temporary file, allowing the Task tooling to analyze results without blocking your terminal session.