Run headless SolidWorks add-in test suites and report pass/fail results.
npx skills add https://github.com/ttsmith21/swcsharpaddin --skill qa-ttsmith21
Please help me install this Agent Skill. Skill: qa Source: https://github.com/ttsmith21/swcsharpaddin/tree/main/.claude/skills/qa Command: npx skills add https://github.com/ttsmith21/swcsharpaddin --skill qa-ttsmith21
Headless QA validation automates verifying code changes by running the full test suite against the SolidWorks add-in, ensuring regressions are caught before release.
Run the QA skill against your local development environment to validate the latest changes.
High-intent search queries and answers about installing and using this skill.
Automate QA validation by running a headless test suite against the SolidWorks add-in to verify build integrity and execute gold-standard test parts. This catches regressions before release without manual intervention.
Headless QA testing runs SolidWorks in headless mode to execute end-to-end test suites without a graphical interface. It streamlines CI pipelines by automating builds, running regression checks, and reporting pass or fail outcomes.
Yes, you can run the QA tests locally to validate the latest code changes. The process builds the main project and QA runner, then executes the full test suite against the SolidWorks add-in in headless mode.
The best way to catch regressions is automating end-to-end QA validation that builds the project, runs all gold-standard test parts in headless mode, and generates comprehensive pass or fail reports for consistent regression checks.
Automated CI testing verifies build integrity by compiling the main project and QA runner before executing tests. If the build fails, the pipeline stops, preventing broken code from executing the gold-standard test suite.
No, you do not need a display server. The QA tests run SolidWorks in headless mode, allowing the test suite to execute within CI pipelines and local environments without requiring a graphical interface.
kurtosis-techBuilds and tests Kurtosis from source on local Docker, compiling Engine, Core, Files Artifacts Expander, CLI, tagging images with git short SHA, and restarting the engine for a clean test environment.
solace-illAnalyze CI logs and JUnit/XML results to detect flaky tests.
atframeworkValidate repository root configurations and dependencies across build, lint, and CI changes.
nikblanchetPlan and implement unit, integration, regression, end-to-end, and manual test coverage.
