Skip to content
cccskills
FreePublished on GitHub

trino-test

Run and troubleshoot Trino integration tests for Gravitino. Choose a connector test set, an individual test file, a catalog, or a Trino version, then inspect progress and failures. The skill also explains the SQL and expected-output files used to add or update test cases.

OriginalShow the original description

Run, debug, and manage Trino integration tests for the Gravitino project.

apache/gravitino3,337 stars(GitHub 3,337 + cccskills 0)
Works withMySQL

Run score Not tested

See how to install

Good for

  • Running the full Trino integration test suite
  • Testing a specific connector or catalog
  • Checking a particular Trino version
  • Adding or fixing SQL test cases

Files included (2)

  • SKILL.md3.1 KB
  • trino-test-guide.md16.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->

/trino-test — Trino Integration Test Skill

This skill helps you run, debug, and manage Trino integration tests for the Gravitino project.

Use this skill whenever the user asks about:

  • running Trino integration tests
  • testing specific connectors (e.g. MySQL)
  • testing specific Trino versions
  • adding or fixing Trino test cases

Documentation Reference

Full guide:

.claude/skills/trino-test-guide.md

Read the guide for complete details on:

  • Test architecture and structure
  • All available parameters and options
  • Test modes (--auto=all | gravitino | none)
  • Adding and modifying tests
  • Expected output format (.txt with % wildcards)
  • Debugging and troubleshooting

Project Root

All commands assume:

cd /home/ubuntu/git/gravitino

Quick Commands

Run all tests

./trino-connector/integration-test/trino-test-tools/trino_integration_test.sh \
  --auto=all

Run specific test set

./trino-connector/integration-test/trino-test-tools/trino_integration_test.sh \
  --auto=all --test_set=jdbc-mysql

Run specific test file

./trino-connector/integration-test/trino-test-tools/trino_integration_test.sh \
  --auto=all --test_set=jdbc-mysql --tester_id=00004

Run specific test catalog with testset

./trino-connector/integration-test/trino-test-tools/trino_integration_test.sh
--auto=all --test_set=tpch --catalog=hive

Test specific Trino version with specific trino connector

./trino-connector/integration-test/trino-test-tools/trino_integration_test.sh \
  --auto=all \
  --trino_version=<VERSION> \
  --trino_connector_dir=<WORKSPACE>/trino-connector/trino-connector-<VERSION_RANGE>/build/libs

Check test status

grep -E "(Test progress|All testers|Total|PASS|FAIL|BUILD) from log

Test Structure

Location:

trino-connector/integration-test/src/test/resources/trino-ci-testset/testsets/

Each test consists of:

  • *.sql — SQL statements to execute
  • *.txt — Expected output
    • Supports % wildcard for flexible matching

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Guide an Apache Gravitino release through its staged process, from tagging and building artifacts to publishing, voting, finalizing, and preparing release notes. Track completed stages, check prerequisites, and handle mock or dry-run workflows with the documented scripts.

  • Preparing a Gravitino release candidate
  • Checking which release stages are complete
  • Running or previewing a release stage
apache/gravitino3.3KUpdated Oct 29, 2026

See all skills by apache

Report a problem with this skill