Before start testing method in components we initialize few things as below
- beforeEach method helps in initializing the values needed for testing
- describe are similar to JUnit class and it are similar to junit class methods which tests particular method in src code
- TestBed is needed while testing both component and html.You need to configure the TestBed before each test, adding any components, modules and services you need for the test. It’s just like configuring an regular @NgModule from scratch, but you just add what you need.
import { async, TestBed } from '@angular/core/testing'; beforeEach(async(() => { TestBed.configureTestingModule({ declarations: [ AppComponent ], providers: [], imports: [] }) .compileComponents(); })); - Using TestBed.createComponent create component instance returns componentFixture Interface. componentFixture is a wrapper over component with additional methods needed for testing. fixture.componentInstance returns instance of component.
beforeEach(() => { . //Returns Component Fixture let fixture = TestBed.createComponent(EmployeeComponent); //Get Instance of Component component = fixture.componentInstance; . . }); - fixture.detectChanges() would allow to check for change in DOM elements before expect or whenever it is referenced for value
- DebugElement, an interface which wraps native element instead of HTML element in idle scenario
- schemas:[NO_ERRORS_SCHEMAS] lets angular testing module to ignore unknown tags in html during testing. Suppose you have used router tags in html
and angular could not recognize the router tag since routerTestingModule is not imported you can use this tag as below to avoid errors.beforeEach(() => { TestBed.configureTestingModule({ declarations: [ EmployeeComponent] schemas:[NO_ERRORS_SCHEMAS] }).compileComponents(); //Testbed to create fixture for component fixture = TestBed.createComponent(EmployeeComponent); //Using fixture to create component and service component = fixture.componentInstance; empService = TestBed.inject(EmpserviceService); });
Simple testing with matchers
- toBeTruthy tells the component is created successfully
- toBe checks for equality of value
- toEqual method does object comparison
- toContain method checks whether value is available in array
fit('Simple component testing', ()=>{
//Checks whether component has been created
expect(component).toBeTruthy();
//Checks whether value returned by function are same
expect(component.getGender(true)).toBe('Male');
//Checks objects are equal and array contain that element
var Names = ['Name1', 'Name2', 'Name3'];
expect(Names).toEqual(['Name1', 'Name2', 'Name3']);
expect(Names).toContain('Name2');
});
Checking DOM Elements
- nativeElement – provides the access to DOM element.This is same as Javascript DOM Element we use for DOM Manipulation.Using nativeElement you can
access all the API methods provided vy Javascript for DOM manipulation like QuerySelector - fixture.detectChanges() – updates the DOM Element after setting the value from testing component. This is similar to refresh once the component value is set the html should be refreshed.
- debugElement– debugElement is similar to nativeElement which has wrapper with some additional methods.It has query, queryAll, queryNode methods
debugElement inturn calls nativeElement to get the values.fixture.debugElement returns the root debugElement from which we query for the nativeElement.. . fixture.debugElement.query(By.css('a')).nativeElement.textContent) fixture.debugElement.query(By.css('#ContactUsId')).nativeElement.textContent) fixture.debugElement.query(By.css('.ContactUsId')).nativeElement.textContent) . . . - The below statement end up the same anchor tag
. fixture.debugElement.query(By.css('a')).nativeElement.textContent) fixture.nativeElement.querySelector('a').textContent .
