Skip to content

oberconcejo/VS-CODE / .agents/skills/angular-developer

angular-developer

Verified

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

FileKindSize
SKILL.mdskill md10.8 KB
references/angular-animations.mdmarkdown3.9 KB
references/angular-aria.mdmarkdown12.3 KB
references/cli.mdmarkdown3.6 KB
references/component-harnesses.mdmarkdown2.8 KB
references/component-styling.mdmarkdown2.5 KB
references/components.mdmarkdown3.3 KB
references/creating-services.mdmarkdown2.6 KB
references/data-resolvers.mdmarkdown1.5 KB
references/define-routes.mdmarkdown1.7 KB
references/defining-providers.mdmarkdown2.2 KB
references/di-fundamentals.mdmarkdown3.5 KB
references/e2e-testing.mdmarkdown1.9 KB
references/effects.mdmarkdown2.7 KB
references/hierarchical-injectors.mdmarkdown2.0 KB
references/host-elements.mdmarkdown2.1 KB
references/injection-context.mdmarkdown1.9 KB
references/inputs.mdmarkdown2.4 KB
references/linked-signal.mdmarkdown2.5 KB
references/loading-strategies.mdmarkdown1.4 KB
references/mcp.mdmarkdown4.0 KB
references/navigate-to-routes.mdmarkdown1.6 KB
references/outputs.mdmarkdown2.5 KB
references/reactive-forms.mdmarkdown3.5 KB
references/rendering-strategies.mdmarkdown1.8 KB
references/resource.mdmarkdown2.7 KB
references/route-animations.mdmarkdown1.6 KB
references/route-guards.mdmarkdown1.4 KB
references/router-lifecycle.mdmarkdown1.5 KB
references/router-testing.mdmarkdown3.8 KB
references/show-routes-with-outlets.mdmarkdown1.6 KB
references/signal-forms.mdmarkdown23.6 KB
references/signals-overview.mdmarkdown2.8 KB
references/tailwind-css.mdmarkdown1.8 KB
references/template-driven-forms.mdmarkdown3.7 KB
references/testing-fundamentals.mdmarkdown2.6 KB

references/testing-fundamentals.md

View on GitHub
# Testing Fundamentals

This guide covers the fundamental principles and practices for writing Angular unit and component tests. Use the runner already configured in the project.

## Core Philosophy: Async-First

Modern Angular applications often schedule state changes asynchronously, especially when using signals or zoneless change detection. Tests should account for this.

Prefer the "Act, Wait, Assert" pattern:

1. **Act:** Update state or perform an action (e.g., set a component input, click a button).
2. **Wait:** Use `await fixture.whenStable()` to allow the framework to process the scheduled update and render the changes.
3. **Assert:** Verify the outcome.

### Basic Test Structure Example

```ts
import {ComponentFixture, TestBed} from '@angular/core/testing';
import {MyComponent} from './my.component';

describe('MyComponent', () => {
  let component: MyComponent;
  let fixture: ComponentFixture<MyComponent>;
  let h1: HTMLElement;

  beforeEach(async () => {
    // 1. Configure the test module
    await TestBed.configureTestingModule({
      imports: [MyComponent],
    }).compileComponents();

    // 2. Create the component fixture
    fixture = TestBed.createComponent(MyComponent);
    component = fixture.componentInstance;
    h1 = fixture.nativeElement.querySelector('h1');
  });

  it('should display the default title', async () => {
    // ACT: (Implicit) Component is created with default state.
    // WAIT for initial data binding.
    await fixture.whenStable();
    // ASSERT the initial state.
    expect(h1.textContent).toContain('Default Title');
  });

  it('should display a different title after a change', async () => {
    // ACT: Change the component's title property.
    component.title.set('New Test Title');

    // WAIT for the asynchronous update to complete.
    await fixture.whenStable();

    // ASSERT the DOM has been updated.
    expect(h1.textContent).toContain('New Test Title');
  });
});
```

## TestBed and ComponentFixture

- **`TestBed`**: The primary utility for creating a test-specific Angular module. Use `TestBed.configureTestingModule({...})` in your `beforeEach` to declare components, provide services, and set up imports needed for your test.
- **`ComponentFixture`**: A handle on the created component instance and its environment.
  - `fixture.componentInstance`: Access the component's class instance.
  - `fixture.nativeElement`: Access the component's root DOM element.
  - `fixture.debugElement`: An Angular-specific wrapper around the `nativeElement` that provides safer, platform-agnostic ways to query the DOM (e.g., `debugElement.query(By.css('p'))`).
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall