How can I test simple navigation with this set up?

[kamok]

Thanks for writing this seed project for testing. I'm currently still learning Ionic 2 and Angular, so this might be an elementary question: How do I test a simple nav.pop(); button?

I have a very simple button that calls a 'goBack()' function when clicked:

@Component({
  selector: 'back-button',
  template: `
  <button ion-button icon-only clear color="light" (click)="goBack()">
    <ion-icon name="arrow-back"></ion-icon>
  </button>
  `
})
export class BackButton {
  constructor(public navCtrl: NavController, public viewCtrl: ViewController) {}

  goBack(): void {
    this.navCtrl.pop();
  }
}

In the tests, I have these expectations:

describe('BackButton', () => {

  beforeEach(async(() => TestUtils.beforeEachCompiler([BackButton]).then(compiled => {
    fixture = compiled.fixture;
    instance = compiled.instance;
    // instance.ViewController = new ViewControllerMock();
  })));

  afterEach(() => {
    fixture.destroy();
  });

  it('initializes', () => {
    expect(instance).not.toBeNull();
  });

  it('goes back a page when pressed', () => {
    fixture.detectChanges();
    spyOn(instance,'goBack');
    TestUtils.eventFire(fixture.nativeElement.querySelectorAll('button')[0], 'click');
    expect(instance.goBack).toHaveBeenCalled();
  });
});

This is all pretty much what you have in the clicker app, but I think the last expectation doesn't really test if nav.pop is triggered, and I don't know the convention of doing so. Please assist if possible.

[lathonez]

I am away at the moment so can't answer in detail. Just spy on instance.nav.pop and check that it was called? This question has nothing to do with "this setup", is more of a "how to unit test" question. You'll get a much better response on stack overflow.

…

On 1 Dec 2016 22:17, "Ka Mok" ***@***.***> wrote: Thanks for writing this seed project for testing. I'm currently still learning Ionic 2 and Angular, so this might be an elementary question: How do I test a simple nav.pop(); button? I have a very simple button that calls a 'goBack()' function when clicked: @component({ selector: 'back-button', template: ` <button ion-button icon-only clear color="light" (click)="goBack()"> <ion-icon name="arrow-back"></ion-icon> </button> ` }) export class BackButton { constructor(public navCtrl: NavController, public viewCtrl: ViewController) {} goBack(): void { this.navCtrl.pop(); } } In the tests, I have these expectations: describe('BackButton', () => { beforeEach(async(() => TestUtils.beforeEachCompiler([BackButton]).then(compiled => { fixture = compiled.fixture; instance = compiled.instance; // instance.ViewController = new ViewControllerMock(); }))); afterEach(() => { fixture.destroy(); }); it('initializes', () => { expect(instance).not.toBeNull(); }); it('goes back a page when pressed', () => { fixture.detectChanges(); spyOn(instance,'goBack'); TestUtils.eventFire(fixture.nativeElement.querySelectorAll('button')[0], 'click'); expect(instance.goBack).toHaveBeenCalled(); }); }); This is all pretty much what you have in the clicker app, but I think the last expectation doesn't really test if nav.pop is triggered, and I don't know the convention of doing so. Please assist if possible. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#184>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AG5tSPf5TYVRzngETY_iVP4FLBjQkd9_ks5rDuUKgaJpZM4LBgrT> .

[kamok]

Thanks. I got feedback from another engineer on this. You're correct.

[lathonez]

#191