https://github.com/angeeks/testing

Clean and Dry your Angular unit tests.
https://github.com/angeeks/testing

angular-testing npm

Last synced: 20 days ago
JSON representation

Clean and Dry your Angular unit tests.

• Host: GitHub
• URL: https://github.com/angeeks/testing
• Owner: angeeks
• Created: 2018-05-27T15:51:56.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2018-06-14T15:50:12.000Z (about 8 years ago)
• Last Synced: 2025-11-16T09:16:30.356Z (8 months ago)
• Topics: angular-testing, npm
• Language: TypeScript
• Homepage:
• Size: 275 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
# Testing

[![npm](https://img.shields.io/npm/dw/@angeeks/testing.svg?style=social)](https://www.npmjs.com/package/@angeeks/testing)

[![npm](https://img.shields.io/npm/v/@angeeks/testing.svg?style=social)](https://www.npmjs.com/package/@angeeks/testing)

[![npm bundle size (minified + gzip)](https://img.shields.io/bundlephobia/minzip/@angeeks/testing.svg?style=social)](https://www.npmjs.com/package/@angeeks/testing)

[![Travis](https://img.shields.io/travis/angeeks/testing.svg?style=flat-square)](https://www.npmjs.com/package/@angeeks/testing)

Clean and Dry your Angular unit tests.

# Why this?

Angular built with great testing tools for unit tests, but its flexibility introduces a lot of redundant code when project's components/services grow. @angeeks/testing aims to provide cleaner ways to write specs for most of common patterns with minimum efforts.

And then, we can get more time for another cup of tea :tea:, cheers.

## spec from official guide

```

import { TestBed, async } from '@angular/core/testing';

import { TediousComponent } from './tedious.component';

descirbe('handtypeed, emotional, typo prone spec title..', () => {

  beforeEach(async(() => {

    TestBed.configureTestingModule({

      declarations: [

        TediousComponent

      ],

    }).compileComponents();

  }));

  // frequent used test pattern

  it('should create the app', async(() => {

    const fixture = TestBed.createComponent(AppComponent);

    const app = fixture.debugElement.componentInstance;

    expect(app).toBeTruthy();

  }));

  // frequent used test pattern

  it(`should have as title 'ngk'`, async(() => {

    const fixture = TestBed.createComponent(AppComponent);

    const app = fixture.debugElement.componentInstance;

    expect(app.title).toEqual('ngk');

  }));

});

```

## With @angeeks/testing

```

import { ComponentSuite as Component } from '@angeeks/testing';

import { TediousComponent as Subject } from './tedious.component';

Component.suite(Subject, (spec) => {

  spec.init();

  spec.expectProperty('title', 'ngk');

});

```

And the report will be like:

```

  ngk-root

    ✓ should be created (68ms)

    ✓ has .title to equal "ngk" (44ms)

```

# Installation

```

  npm i -D @angeeks/testing

```

# APIs

## Suite.on(Subject, callback: (spec: Suite) => {})

## Suite.suite(Subject, callback: (spec: Suite) => {})

- Subject for the spec

- callback for jasmine describe, with spec instance keep common variables

## Suite.fon(Subject, callback: (spec: Suite) => {})

## Suite.fsuite(Subject, callback: (spec: Suite) => {})

Same like fdescribe