Igniteui Angular Testing logo

Igniteui Angular Testing

Organization
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.

Overview

PublisherIgniteUI
Repositoryigniteui-angular
Skill nameigniteui-angular-testing
Stars
599
Forks
161
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by IgniteUI on GitHub. Read the source before you install it.

Installation

Install the Igniteui Angular Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/IgniteUI/igniteui-angular.git /tmp/igniteui-angular
mkdir -p .claude/skills
cp -r /tmp/igniteui-angular/.agents/skills/igniteui-angular-testing .claude/skills/igniteui-angular-testing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Igniteui Angular Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Igniteui Angular Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Igniteui Angular Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

ScenarioCommand
All library tests (slow — runs everything)npm run test:lib
Flat grid tests onlynpm run test:lib:grid
Tree grid tests onlynpm run test:lib:tgrid
Hierarchical grid tests onlynpm run test:lib:hgrid
Pivot grid tests onlynpm 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 testsnpm run test:lib:perf
Schematics + migrationsnpm run test:schematics
Sass/style logicnpm run test:styles
i18n resource validationnpm run test:i18n

Decision Guide

  1. 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 fileUsed by
karma.conf.jstest:lib (all tests)
karma.grid.conf.jstest:lib:grid
karma.tree-grid.conf.jstest:lib:tgrid
karma.hierarchical-grid.conf.jstest:lib:hgrid
karma.pivot-grid.conf.jstest:lib:pgrid
karma.non-grid.conf.jstest:lib:others
karma.watch.conf.jstest:lib:watch
karma.test-perf.conf.jstest:lib:perf (performance)

All configs are in projects/igniteui-angular/.

Key Paths

PathPurpose
projects/igniteui-angular/test-utils/Shared test helpers and utilities
projects/igniteui-angular/src/test.tsKarma test entry point
coverage/Code coverage output

Related Skills

Frequently asked questions

What does the Igniteui Angular Testing AI skill do?

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.

Why use Igniteui Angular Testing on TypingMind?

Because you install it once and use it with any model. Igniteui Angular Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Igniteui Angular Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IgniteUI/igniteui-angular/tree/master/.agents/skills/igniteui-angular-testing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Igniteui Angular Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Igniteui Angular Testing?

As many as you like. As long as a model supports skills, you can use Igniteui Angular Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Igniteui Angular Testing AI skill free?

It is published on GitHub by IgniteUI. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇