test

Build, lint, and test code changes with yarn commands.

368|98|Updated Jan 25, 2021

Search Tags:#typescript #verification #build #quality #lint #ci #tests

Ready to run

npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill test-hardisgroupcom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/hardisgroupcom/sfdx-hardis/tree/main/.claude/skills/test
Command: npx skills add https://github.com/hardisgroupcom/sfdx-hardis --skill test-hardisgroupcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build, lint, and run tests to verify the implementation as part of the contribution workflow.

Core Features & Use Cases

Compile and type-check the code to catch build-time errors.
Lint and enforce coding standards to maintain quality.
Run unit and integration tests to validate behavior after changes.

Quick Start

Run yarn compile, yarn lint, and yarn test to verify your changes.

Frequently Asked Questions about test

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

FAQPage Schema

How do I verify code quality before merging TypeScript changes?▼

To verify code quality before merging TypeScript changes, you can automate building, linting, and running tests. This workflow enforces TypeScript compilation, coding standards, and test suite validation to ensure implementation correctness.

What is the best way to automate TypeScript compilation and lint checks for a contribution workflow?▼

Automating TypeScript compilation and lint checks involves running dedicated commands like yarn compile and yarn lint to catch build-time errors and enforce standards. Applying this to your contribution workflow verifies code changes consistently before merging.

Can I run unit and integration tests automatically after implementing code changes?▼

Yes, you can run unit and integration tests automatically after implementing code changes. Executing the test suite via yarn test validates behavior and ensures your new changes do not break existing repository functionality.

Does this code verification workflow require specific dependencies for CI environments?▼

No specific dependencies are required for this code verification workflow in CI environments. It operates independently to apply build, lint, and test validation across contributor workflows without external component dependencies.

Why should I run lint checks before running the test suite?▼

Running lint checks before the test suite enforces coding standards and catches syntax errors early. This approach maintains repository quality and prevents unnecessary test execution on improperly formatted TypeScript code.