ptoas-test-framework-guidance

Place PTOAS tests in lit, VPTO, or TileLang ST frameworks with validation commands.

30|74|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/hw-native-sys/PTOAS --skill ptoas-test-framework-guidance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ptoas-test-framework-guidance
Source: https://github.com/hw-native-sys/PTOAS/tree/main/.codex/skills/ptoas-test-framework-guidance
Command: npx skills add https://github.com/hw-native-sys/PTOAS --skill ptoas-test-framework-guidance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents PTOAS tests from being placed in directories or harnesses that cannot discover or validate them, reducing misleading coverage and framework-specific failures.

Core Features & Use Cases

  • Framework Selection: Choose between compiler lit tests, generic PTO lowering tests, VPTO backend tests, runtime validation cases, and TileLang ST system tests.
  • Discovery Guidance: Follow the required file layouts, naming conventions, RUN lines, and testcase structures for each supported framework.
  • Validation Workflows: Use the appropriate lit, VPTO runtime, or TileLang ST commands to verify test visibility and behavior.
  • Use Case: When adding a VPTO kernel correctness test, place the required runtime files under the VPTO case directory and validate execution through the standard runtime harness instead of adding simulator expectations to a lit test.

Quick Start

Use this skill to determine the correct PTOAS test framework and validation command for the test you are adding or relocating.

Frequently Asked Questions about ptoas-test-framework-guidance

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

FAQPage Schema
How do I place PTOAS tests in the correct framework for lit and runtime validation?

Placing PTOAS tests correctly requires matching the test type—lit compiler regression, VPTO runtime, or TileLang ST—to its specific directory layout and discovery conventions. This ensures the test is discovered and validates the intended behavior accurately.

What is the difference between lit compiler regressions and VPTO runtime cases in PTOAS?

Lit compiler regressions use FileCheck to validate PTO and VPTO lowering checks, while VPTO runtime cases require placing kernel correctness files under the VPTO case directory and validating execution through a standard runtime harness.

Why does my PTOAS test fail to be discovered by the lit or TileLang ST framework?

PTOAS tests fail discovery when placed in directories or harnesses that do not support the required file layouts, naming conventions, or RUN lines for the specific lit, VPTO, or TileLang ST validation framework.

When do I need to use FileCheck or runtime assertions for PTOAS test validation?

You need FileCheck for lit compiler regressions and PTO lowering checks to verify intermediate output, whereas runtime assertions are required for VPTO runtime cases and TileLang ST system tests to validate actual execution behavior.

Can I add VPTO kernel correctness expectations directly to a lit test?

No, you should not add simulator expectations for VPTO kernel correctness to a lit test. Instead, place the required runtime files under the VPTO case directory and validate execution through the standard runtime harness.

What validation commands are used for TileLang ST system tests and PTOAS?

TileLang ST system tests use the corresponding TileLang ST validation commands to verify test visibility and behavior, while lit tests use standard lit commands and VPTO cases use specific runtime harness commands.