Georgios Kalpakas
4f37f86433
`innerText` is not supported in Firefox prior to v45. In most cases (at least the ones we are interested in), `innerText` and `textContent` work equally well, but `textContent` is more performant (as it doesn't require a reflow). From [MDN][1] on the differences of `innerText` vs `textContent`: > - [...] > - `innerText` is aware of style and will not return the text of hidden > elements, whereas `textContent` will. > - As `innerText` is aware of CSS styling, it will trigger a reflow, whereas > `textContent` will not. > - [...] [1]: https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent#Differences_from_innerText Fixes #17585
34 lines
964 B
TypeScript
34 lines
964 B
TypeScript
import { AppComponent } from './app.component';
|
|
|
|
import { async, ComponentFixture, TestBed } from '@angular/core/testing';
|
|
import { By } from '@angular/platform-browser';
|
|
import { DebugElement } from '@angular/core';
|
|
|
|
describe('AppComponent', function () {
|
|
let de: DebugElement;
|
|
let comp: AppComponent;
|
|
let fixture: ComponentFixture<AppComponent>;
|
|
|
|
beforeEach(async(() => {
|
|
TestBed.configureTestingModule({
|
|
declarations: [ AppComponent ]
|
|
})
|
|
.compileComponents();
|
|
}));
|
|
|
|
beforeEach(() => {
|
|
fixture = TestBed.createComponent(AppComponent);
|
|
comp = fixture.componentInstance;
|
|
de = fixture.debugElement.query(By.css('h1'));
|
|
});
|
|
|
|
it('should create component', () => expect(comp).toBeDefined() );
|
|
|
|
it('should have expected <h1> text', () => {
|
|
fixture.detectChanges();
|
|
const h1 = de.nativeElement;
|
|
expect(h1.textContent).toMatch(/angular/i,
|
|
'<h1> should say something about "Angular"');
|
|
});
|
|
});
|