igniteui-angular-testing

Run Ignite UI for Angular test suites with Karma and Jasmine.

601|160|Updated Feb 11, 2016
One-click install
npx skills add https://github.com/IgniteUI/igniteui-angular --skill igniteui-angular-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: igniteui-angular-testing
Source: https://github.com/IgniteUI/igniteui-angular/tree/main/.github/skills/igniteui-angular-testing
Command: npx skills add https://github.com/IgniteUI/igniteui-angular --skill igniteui-angular-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides quick-access guidance to run and understand Ignite UI for Angular test suites, reducing setup time and guesswork during development and CI.

Core Features & Use Cases

  • Full library test runs covering the entire test surface
  • Grid-specific (grid, tgrid, hgrid, pgrid) and non-grid test suites
  • Watch mode and auxiliary test suites (schematics, styles, i18n)
  • Clear guidance on selecting the right tests for CI and local development

Quick Start

Run npm run test:lib to execute the full library test suite.

Frequently Asked Questions about igniteui-angular-testing

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

FAQPage Schema
How do I run the full Ignite UI for Angular test suite?

Run the full Ignite UI Angular test suite by executing `npm run test:lib` from the repository root. This command validates the entire library surface using the configured Karma and Jasmine test environment.

What testing framework does Ignite UI for Angular use?

Ignite UI for Angular uses the Karma test runner combined with the Jasmine testing framework. Test workflows are configured through specific Karma configuration files to validate library changes.

How do I execute only grid-specific tests for Ignite UI Angular?

Execute grid-specific tests by targeting the grid, tgrid, hgrid, and pgrid test suites. You can isolate these configurations to validate grid components independently from non-grid tests.

Can I run auxiliary tests like schematics, styles, and i18n in Ignite UI Angular?

Yes, you can run auxiliary tests for schematics, styles, and i18n. The test workflow supports executing these specific suites alongside core library tests in both local development and CI contexts.

Do I need to run npm install at the repo root before testing Ignite UI Angular?

Yes, running `npm install` at the repository root is required before testing Ignite UI Angular. This ensures the environment is fully set up with the necessary dependencies and Karma configurations.

What is the best way to select the right tests for Ignite UI Angular CI workflows?

Select the right tests for CI workflows by referencing the appropriate Karma configs and test utilities. You can choose between full library, grid-specific, non-grid, or auxiliary suites based on your validation scope.