How do I install the Igniteui Angular Testing skill?

Run npx skillmds@latest add igniteui/igniteui-angular-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Igniteui Angular Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Igniteui Angular Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Igniteui Angular Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Igniteui Angular Testing?

igniteui (@igniteui) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Igniteui Angular Testing by igniteui

Name: Igniteui Angular Testing
Author: igniteui

Igniteui Angular Testing

Quick-reference for running Ignite UI for Angular test suites. Covers the full test run (`test:lib`), grid-specific suites (grid, tree-grid, hierarchical-grid, pivot-grid), non-grid tests, watch mode, and auxiliary test suites (schematics, styles, i18n). Use when an agent needs to run, select, or understand the test infrastructure. Do NOT use for building — use igniteui-angular-build instead. Do NOT use for linting — use igniteui-angular-linting instead.

igniteui 2364682 3.7 KB Updated Sep 17, 2026

File contents

Ignite UI for Angular — Testing

Quick-reference card for the core test commands for the main igniteui-angular library plus schematics, styles, and i18n suites.

Prerequisites

Run npm install at the repo root.
Schematics tests normally run from source and do not require a build first. Only run npm run build:schematics and npm run build:migrations when you specifically want to validate the compiled schematics or migrations output.
For performance tests: run npm run build:lib first, or at minimum npm run build:styles, because test:lib:perf loads dist/igniteui-angular/styles/igniteui-angular.css.

Test Runner

Karma + Jasmine for all library unit tests.
Karma configs live in projects/igniteui-angular/karma*.conf.js.
Coverage reports are written to coverage/.

Choosing the Right Command

Scenario	Command
All library tests (slow — runs everything)	`npm run test:lib`
Flat grid tests only	`npm run test:lib:grid`
Tree grid tests only	`npm run test:lib:tgrid`
Hierarchical grid tests only	`npm run test:lib:hgrid`
Pivot grid tests only	`npm run test:lib:pgrid`
All non-grid tests (components, directives, services)	`npm run test:lib:others`
Watch mode (re-runs on file changes, for dev loop)	`npm run test:lib:watch`
Performance tests	`npm run test:lib:perf`
Schematics + migrations	`npm run test:schematics`
Sass/style logic	`npm run test:styles`
i18n resource validation	`npm run test:i18n`

Decision Guide

Working on a grid component? → Use the matching grid command (test:lib:grid, test:lib:tgrid, test:lib:hgrid, or test:lib:pgrid).
Working on a non-grid component or directive? → Use test:lib:others.
Iterating quickly during development? → Use test:lib:watch.
Edited a migration or schematic? → Use test:schematics. Build first only if you also need to validate compiled output.
Running performance tests? → Build first (build:lib or at least build:styles), then use test:lib:perf.
Changed Sass theme logic? → Use test:styles.
Changed i18n resource strings? → Use test:i18n.
Final verification before marking work complete? → Use test:lib (full suite).

Karma Configs

Config file	Used by
`karma.conf.js`	`test:lib` (all tests)
`karma.grid.conf.js`	`test:lib:grid`
`karma.tree-grid.conf.js`	`test:lib:tgrid`
`karma.hierarchical-grid.conf.js`	`test:lib:hgrid`
`karma.pivot-grid.conf.js`	`test:lib:pgrid`
`karma.non-grid.conf.js`	`test:lib:others`
`karma.watch.conf.js`	`test:lib:watch`
`karma.test-perf.conf.js`	`test:lib:perf` (performance)

All configs are in projects/igniteui-angular/.

Key Paths

Path	Purpose
`projects/igniteui-angular/test-utils/`	Shared test helpers and utilities
`projects/igniteui-angular/src/test.ts`	Karma test entry point
`coverage/`	Code coverage output

Related Skills

igniteui-angular-build — Building the library
igniteui-angular-linting — Linting code and styles

---name: igniteui-angular-testingdescription: Quick-reference for running Ignite UI for Angular test suites. Covers the full test run (`test:lib`), grid-specific suites (grid, tree-grid, hierarchical-grid, pivot-grid), non-grid tests, watch mode, and auxiliary test suites (schematics, styles, i18n). Use when an agent needs to run, select, or understand the test infrastructure. Do NOT use for building — use igniteui-angular-build instead. Do NOT use for linting — use igniteui-angular-linting instead.---# Ignite UI for Angular — TestingQuick-reference card for the core test commands for the main igniteui-angular library plus schematics, styles, and i18n suites.## Prerequisites- Run `npm install` at the repo root.- Schematics tests normally run from source and do not require a build first. Only run `npm run build:schematics` and `npm run build:migrations` when you specifically want to validate the compiled schematics or migrations output.- For performance tests: run `npm run build:lib` first, or at minimum `npm run build:styles`, because `test:lib:perf` loads `dist/igniteui-angular/styles/igniteui-angular.css`.## Test Runner- **Karma + Jasmine** for all library unit tests.- Karma configs live in `projects/igniteui-angular/karma*.conf.js`.- Coverage reports are written to `coverage/`.## Choosing the Right Command| Scenario | Command ||---|---|| **All library tests** (slow — runs everything) | `npm run test:lib` || **Flat grid tests** only | `npm run test:lib:grid` || **Tree grid tests** only | `npm run test:lib:tgrid` || **Hierarchical grid tests** only | `npm run test:lib:hgrid` || **Pivot grid tests** only | `npm run test:lib:pgrid` || **All non-grid tests** (components, directives, services) | `npm run test:lib:others` || **Watch mode** (re-runs on file changes, for dev loop) | `npm run test:lib:watch` || **Performance tests** | `npm run test:lib:perf` || **Schematics + migrations** | `npm run test:schematics` || **Sass/style logic** | `npm run test:styles` || **i18n resource validation** | `npm run test:i18n` |### Decision Guide1. **Working on a grid component?** → Use the matching grid command (`test:lib:grid`, `test:lib:tgrid`, `test:lib:hgrid`, or `test:lib:pgrid`).2. **Working on a non-grid component or directive?** → Use `test:lib:others`.3. **Iterating quickly during development?** → Use `test:lib:watch`.4. **Edited a migration or schematic?** → Use `test:schematics`. Build first only if you also need to validate compiled output.5. **Running performance tests?** → Build first (`build:lib` or at least `build:styles`), then use `test:lib:perf`.6. **Changed Sass theme logic?** → Use `test:styles`.7. **Changed i18n resource strings?** → Use `test:i18n`.8. **Final verification before marking work complete?** → Use `test:lib` (full suite).## Karma Configs| Config file | Used by ||---|---|| `karma.conf.js` | `test:lib` (all tests) || `karma.grid.conf.js` | `test:lib:grid` || `karma.tree-grid.conf.js` | `test:lib:tgrid` || `karma.hierarchical-grid.conf.js` | `test:lib:hgrid` || `karma.pivot-grid.conf.js` | `test:lib:pgrid` || `karma.non-grid.conf.js` | `test:lib:others` || `karma.watch.conf.js` | `test:lib:watch` || `karma.test-perf.conf.js` | `test:lib:perf` (performance) |All configs are in `projects/igniteui-angular/`.## Key Paths| Path | Purpose ||---|---|| `projects/igniteui-angular/test-utils/` | Shared test helpers and utilities || `projects/igniteui-angular/src/test.ts` | Karma test entry point || `coverage/` | Code coverage output |## Related Skills- [`igniteui-angular-build`](../igniteui-angular-build/SKILL.md) — Building the library- [`igniteui-angular-linting`](../igniteui-angular-linting/SKILL.md) — Linting code and styles

Frequently asked questions