Angular unit test a prop is never undefined










1















I don't understand why on earth
this simple test doesn't work.



BannerComponent should not have welcome message after construction
Expected 'welcome' to be undefined.


// Component



@Component(
selector: 'iwdf-banner',
template: `
<p>
me
</p>
`,
styles:
)
export class BannerComponent implements OnInit
me: string;
constructor()
ngOnInit()
this.me = 'welcome';




// Test



describe('BannerComponent', () => 
let component: BannerComponent;
let fixture: ComponentFixture<BannerComponent>;

beforeEach(async(() =>
TestBed.configureTestingModule(
declarations: [ BannerComponent ]
)
.compileComponents();
));

beforeEach(() =>
fixture = TestBed.createComponent(BannerComponent);
component = fixture.componentInstance;
fixture.detectChanges();
);

it('should create', () =>
expect(component).toBeTruthy();
);

it('should not have welcome message after construction', () =>
expect(component.me).toBeUndefined();
);

it('should welcome logged in user after Angular calls ngOnInit', () =>
component.ngOnInit();
expect(component.me).toContain('welcome');
);
);









share|improve this question




























    1















    I don't understand why on earth
    this simple test doesn't work.



    BannerComponent should not have welcome message after construction
    Expected 'welcome' to be undefined.


    // Component



    @Component(
    selector: 'iwdf-banner',
    template: `
    <p>
    me
    </p>
    `,
    styles:
    )
    export class BannerComponent implements OnInit
    me: string;
    constructor()
    ngOnInit()
    this.me = 'welcome';




    // Test



    describe('BannerComponent', () => 
    let component: BannerComponent;
    let fixture: ComponentFixture<BannerComponent>;

    beforeEach(async(() =>
    TestBed.configureTestingModule(
    declarations: [ BannerComponent ]
    )
    .compileComponents();
    ));

    beforeEach(() =>
    fixture = TestBed.createComponent(BannerComponent);
    component = fixture.componentInstance;
    fixture.detectChanges();
    );

    it('should create', () =>
    expect(component).toBeTruthy();
    );

    it('should not have welcome message after construction', () =>
    expect(component.me).toBeUndefined();
    );

    it('should welcome logged in user after Angular calls ngOnInit', () =>
    component.ngOnInit();
    expect(component.me).toContain('welcome');
    );
    );









    share|improve this question


























      1












      1








      1








      I don't understand why on earth
      this simple test doesn't work.



      BannerComponent should not have welcome message after construction
      Expected 'welcome' to be undefined.


      // Component



      @Component(
      selector: 'iwdf-banner',
      template: `
      <p>
      me
      </p>
      `,
      styles:
      )
      export class BannerComponent implements OnInit
      me: string;
      constructor()
      ngOnInit()
      this.me = 'welcome';




      // Test



      describe('BannerComponent', () => 
      let component: BannerComponent;
      let fixture: ComponentFixture<BannerComponent>;

      beforeEach(async(() =>
      TestBed.configureTestingModule(
      declarations: [ BannerComponent ]
      )
      .compileComponents();
      ));

      beforeEach(() =>
      fixture = TestBed.createComponent(BannerComponent);
      component = fixture.componentInstance;
      fixture.detectChanges();
      );

      it('should create', () =>
      expect(component).toBeTruthy();
      );

      it('should not have welcome message after construction', () =>
      expect(component.me).toBeUndefined();
      );

      it('should welcome logged in user after Angular calls ngOnInit', () =>
      component.ngOnInit();
      expect(component.me).toContain('welcome');
      );
      );









      share|improve this question
















      I don't understand why on earth
      this simple test doesn't work.



      BannerComponent should not have welcome message after construction
      Expected 'welcome' to be undefined.


      // Component



      @Component(
      selector: 'iwdf-banner',
      template: `
      <p>
      me
      </p>
      `,
      styles:
      )
      export class BannerComponent implements OnInit
      me: string;
      constructor()
      ngOnInit()
      this.me = 'welcome';




      // Test



      describe('BannerComponent', () => 
      let component: BannerComponent;
      let fixture: ComponentFixture<BannerComponent>;

      beforeEach(async(() =>
      TestBed.configureTestingModule(
      declarations: [ BannerComponent ]
      )
      .compileComponents();
      ));

      beforeEach(() =>
      fixture = TestBed.createComponent(BannerComponent);
      component = fixture.componentInstance;
      fixture.detectChanges();
      );

      it('should create', () =>
      expect(component).toBeTruthy();
      );

      it('should not have welcome message after construction', () =>
      expect(component.me).toBeUndefined();
      );

      it('should welcome logged in user after Angular calls ngOnInit', () =>
      component.ngOnInit();
      expect(component.me).toContain('welcome');
      );
      );






      angular unit-testing






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 18:29









      yurzui

      102k11208224




      102k11208224










      asked Nov 15 '18 at 18:15









      WhisherWhisher

      11.1k2282148




      11.1k2282148






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Calling TestBed.createComponent will call the constructor of the component, but not any lifecycle hooks.



          The OnInit lifecycle hook will be called the first time you call fixture.detectChanges(), which you do before every test. So that's why me has the value welcome instead of being undefined.



          You can fix this by removing fixture.detectChanges() from the beforeEach, and moving it to individual tests that need it (which will be all but that one failing test). You do not need to call ngOnInit manually on that last test once you replace the line with fixture.detectChanges().



          Calling ngOnInit manually might be useful if you want to test your component without the angular testbed - you would then have to take care of the dependencies and lifecycles yourself, which I don't suggest.






          share|improve this answer
































            1














            Well, TestBed does run all the nescessary lifecycle hooks on detect changes. So it is to be expected that the variable is defined. Don't use fixture.detectChanges(). That one runs the hook.






            share|improve this answer






















              Your Answer






              StackExchange.ifUsing("editor", function ()
              StackExchange.using("externalEditor", function ()
              StackExchange.using("snippets", function ()
              StackExchange.snippets.init();
              );
              );
              , "code-snippets");

              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "1"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325586%2fangular-unit-test-a-prop-is-never-undefined%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              Calling TestBed.createComponent will call the constructor of the component, but not any lifecycle hooks.



              The OnInit lifecycle hook will be called the first time you call fixture.detectChanges(), which you do before every test. So that's why me has the value welcome instead of being undefined.



              You can fix this by removing fixture.detectChanges() from the beforeEach, and moving it to individual tests that need it (which will be all but that one failing test). You do not need to call ngOnInit manually on that last test once you replace the line with fixture.detectChanges().



              Calling ngOnInit manually might be useful if you want to test your component without the angular testbed - you would then have to take care of the dependencies and lifecycles yourself, which I don't suggest.






              share|improve this answer





























                0














                Calling TestBed.createComponent will call the constructor of the component, but not any lifecycle hooks.



                The OnInit lifecycle hook will be called the first time you call fixture.detectChanges(), which you do before every test. So that's why me has the value welcome instead of being undefined.



                You can fix this by removing fixture.detectChanges() from the beforeEach, and moving it to individual tests that need it (which will be all but that one failing test). You do not need to call ngOnInit manually on that last test once you replace the line with fixture.detectChanges().



                Calling ngOnInit manually might be useful if you want to test your component without the angular testbed - you would then have to take care of the dependencies and lifecycles yourself, which I don't suggest.






                share|improve this answer



























                  0












                  0








                  0







                  Calling TestBed.createComponent will call the constructor of the component, but not any lifecycle hooks.



                  The OnInit lifecycle hook will be called the first time you call fixture.detectChanges(), which you do before every test. So that's why me has the value welcome instead of being undefined.



                  You can fix this by removing fixture.detectChanges() from the beforeEach, and moving it to individual tests that need it (which will be all but that one failing test). You do not need to call ngOnInit manually on that last test once you replace the line with fixture.detectChanges().



                  Calling ngOnInit manually might be useful if you want to test your component without the angular testbed - you would then have to take care of the dependencies and lifecycles yourself, which I don't suggest.






                  share|improve this answer















                  Calling TestBed.createComponent will call the constructor of the component, but not any lifecycle hooks.



                  The OnInit lifecycle hook will be called the first time you call fixture.detectChanges(), which you do before every test. So that's why me has the value welcome instead of being undefined.



                  You can fix this by removing fixture.detectChanges() from the beforeEach, and moving it to individual tests that need it (which will be all but that one failing test). You do not need to call ngOnInit manually on that last test once you replace the line with fixture.detectChanges().



                  Calling ngOnInit manually might be useful if you want to test your component without the angular testbed - you would then have to take care of the dependencies and lifecycles yourself, which I don't suggest.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 15 '18 at 18:59

























                  answered Nov 15 '18 at 18:46









                  Kevin DoyonKevin Doyon

                  2,2162233




                  2,2162233























                      1














                      Well, TestBed does run all the nescessary lifecycle hooks on detect changes. So it is to be expected that the variable is defined. Don't use fixture.detectChanges(). That one runs the hook.






                      share|improve this answer



























                        1














                        Well, TestBed does run all the nescessary lifecycle hooks on detect changes. So it is to be expected that the variable is defined. Don't use fixture.detectChanges(). That one runs the hook.






                        share|improve this answer

























                          1












                          1








                          1







                          Well, TestBed does run all the nescessary lifecycle hooks on detect changes. So it is to be expected that the variable is defined. Don't use fixture.detectChanges(). That one runs the hook.






                          share|improve this answer













                          Well, TestBed does run all the nescessary lifecycle hooks on detect changes. So it is to be expected that the variable is defined. Don't use fixture.detectChanges(). That one runs the hook.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 15 '18 at 18:18









                          pascalpuetzpascalpuetz

                          37619




                          37619



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Stack Overflow!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325586%2fangular-unit-test-a-prop-is-never-undefined%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              這個網誌中的熱門文章

                              What does pagestruct do in Eviews?

                              Dutch intervention in Lombok and Karangasem

                              Channel Islands