Build, run, and debug the LPTS SQL transpilation test suite.
npx skills add https://github.com/cwida/lpts --skill run-tests-cwida
Please help me install this Agent Skill. Skill: run-tests Source: https://github.com/cwida/lpts/tree/main/.claude/skills/run-tests Command: npx skills add https://github.com/cwida/lpts --skill run-tests-cwida
Manually building the LPTS extension, running test suites, tracking assertion results, and diagnosing test crashes or transpilation failures is time-consuming and prone to oversight, especially when iterating on new features or dialect support.
Use the run-tests skill to run the full LPTS test suite and get a summary of all passed and failed assertions.
High-intent search queries and answers about installing and using this skill.
Automate DuckDB test suite execution by building the LPTS extension and running targeted test files to verify SQL transpilation regression. The workflow returns exact passed and failed assertion counts, surfacing failing test names with expected versus actual output for quick identification.
Debug unsupported query patterns causing test crashes using guided troubleshooting steps for AST and logical plan inspection. This approach resolves transpilation edge cases encountered during dialect compatibility validation by identifying exact query failures.
You need the LPTS repository build tools and DuckDB test runner to execute regression tests for new SQL dialect features. Optional TPC-H and SQL Storm test datasets provide comprehensive test coverage for validating query correctness.
Automated test reporting identifies failing SQL assertions by returning exact counts of passed and failed assertions, then surfacing failing test names with expected versus actual output. This clear result reporting enables quick issue identification during test debugging.
Running individual test files helps with crash investigation for unsupported query patterns by isolating specific transpilation failures. This targeted execution avoids rebuilding the entire suite, streamlining the identification of unsupported query errors.
You can use TPC-H and SQL Storm datasets for comprehensive query correctness validation in DuckDB. These optional test datasets expand test coverage to ensure robust SQL transpilation across various dialect compatibility scenarios.
kindoflukeIdentify optimal Sirius configurations for TPC-H workloads across scale factors.
cwidaDocument the LPTS pipeline converting DuckDB logical plans to CTE-based SQL strings.
cwidaDocuments LPTS DuckDB extension DDL syntax, including pragmas, table functions, dialects, and known limitations.
eng-vmessiahAutomate regression tests validating API response shapes and state integrity.
