As soon as protractor execute first it block gives an error :-Error while waiting for Protractor to sync with the page










0















describe('Login Scenarios', function () 

it('First IT block', function ()
browser.get('http:XXXXXXXXXXXXXXXXXXXX');
browser.manage().window().maximize();
LoginPage.Login(USERNAME, PASSWORD);

);
it('Second IT block', function ()
browser.waitForAngularEnabled(false);
Properties.logout.click();
Properties.confirmlogout.click();
AutomationUtility.hold();
);
);


When I keep all the code in first IT block it runs fine but when divided into multiple test cases protractor will execute first IT block only, after that it gives an error message as:-



Error: Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details


Then, Protractor does not close the browser and gives the error messages of not finding element etc as protractor running test cases in chronological order.










share|improve this question




























    0















    describe('Login Scenarios', function () 

    it('First IT block', function ()
    browser.get('http:XXXXXXXXXXXXXXXXXXXX');
    browser.manage().window().maximize();
    LoginPage.Login(USERNAME, PASSWORD);

    );
    it('Second IT block', function ()
    browser.waitForAngularEnabled(false);
    Properties.logout.click();
    Properties.confirmlogout.click();
    AutomationUtility.hold();
    );
    );


    When I keep all the code in first IT block it runs fine but when divided into multiple test cases protractor will execute first IT block only, after that it gives an error message as:-



    Error: Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details


    Then, Protractor does not close the browser and gives the error messages of not finding element etc as protractor running test cases in chronological order.










    share|improve this question


























      0












      0








      0








      describe('Login Scenarios', function () 

      it('First IT block', function ()
      browser.get('http:XXXXXXXXXXXXXXXXXXXX');
      browser.manage().window().maximize();
      LoginPage.Login(USERNAME, PASSWORD);

      );
      it('Second IT block', function ()
      browser.waitForAngularEnabled(false);
      Properties.logout.click();
      Properties.confirmlogout.click();
      AutomationUtility.hold();
      );
      );


      When I keep all the code in first IT block it runs fine but when divided into multiple test cases protractor will execute first IT block only, after that it gives an error message as:-



      Error: Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details


      Then, Protractor does not close the browser and gives the error messages of not finding element etc as protractor running test cases in chronological order.










      share|improve this question
















      describe('Login Scenarios', function () 

      it('First IT block', function ()
      browser.get('http:XXXXXXXXXXXXXXXXXXXX');
      browser.manage().window().maximize();
      LoginPage.Login(USERNAME, PASSWORD);

      );
      it('Second IT block', function ()
      browser.waitForAngularEnabled(false);
      Properties.logout.click();
      Properties.confirmlogout.click();
      AutomationUtility.hold();
      );
      );


      When I keep all the code in first IT block it runs fine but when divided into multiple test cases protractor will execute first IT block only, after that it gives an error message as:-



      Error: Error while waiting for Protractor to sync with the page: "both angularJS testability and angular testability are undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details


      Then, Protractor does not close the browser and gives the error messages of not finding element etc as protractor running test cases in chronological order.







      protractor






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 13:40









      Vladimir Vagaytsev

      2,17592327




      2,17592327










      asked Nov 14 '18 at 11:50









      aditya birthereaditya birthere

      12




      12






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Move browser.waitForAngularEnabled(false); to configuration protractor.conf.js file into onPrepare section.



          export let config = 
          ...
          ...
          onPrepare () =>
          browser.waitForAngularEnabled(false);
          ...
          ,
          ...
          ...
          ;


          Or disable wait for angular before browser.get(), then enable after browser.get()



          describe('Login Scenarios', function () 

          it('First IT block', function ()
          // disable if opening page is non-angular page
          browser.waitForAngularEnabled(false);
          browser.get('http:XXXXXXXXXXXXXXXXXXXX');

          // revert back to enable, after the non-angular page opened.
          browser.waitForAngularEnabled(true);

          browser.manage().window().maximize();
          LoginPage.Login(USERNAME, PASSWORD);

          );
          it('Second IT block', function ()
          Properties.logout.click();
          Properties.confirmlogout.click();
          AutomationUtility.hold();
          );
          );





          share|improve this answer

























          • Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

            – aditya birthere
            Nov 14 '18 at 12:55












          • tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

            – aditya birthere
            Nov 15 '18 at 7:04












          • You should add explicit waiter before action with element.

            – Oleksii
            Nov 15 '18 at 7:11











          • Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

            – aditya birthere
            Nov 15 '18 at 7:42











          • so, the error is right. Sorry but it is another question.

            – Oleksii
            Nov 15 '18 at 9:35


















          0














          I am able to resolve by putting URL in onPrepare section. In to configuration protractor.conf.js file:-



          return browser.get('http://XXXXXXXXXXXXXXXXXXXX/login');



          Thus the protractor is not failing when clicked on the login button. Also not getting any Error while waiting for Protractor to sync with the page.






          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%2f53299589%2fas-soon-as-protractor-execute-first-it-block-gives-an-error-error-while-waitin%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














            Move browser.waitForAngularEnabled(false); to configuration protractor.conf.js file into onPrepare section.



            export let config = 
            ...
            ...
            onPrepare () =>
            browser.waitForAngularEnabled(false);
            ...
            ,
            ...
            ...
            ;


            Or disable wait for angular before browser.get(), then enable after browser.get()



            describe('Login Scenarios', function () 

            it('First IT block', function ()
            // disable if opening page is non-angular page
            browser.waitForAngularEnabled(false);
            browser.get('http:XXXXXXXXXXXXXXXXXXXX');

            // revert back to enable, after the non-angular page opened.
            browser.waitForAngularEnabled(true);

            browser.manage().window().maximize();
            LoginPage.Login(USERNAME, PASSWORD);

            );
            it('Second IT block', function ()
            Properties.logout.click();
            Properties.confirmlogout.click();
            AutomationUtility.hold();
            );
            );





            share|improve this answer

























            • Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

              – aditya birthere
              Nov 14 '18 at 12:55












            • tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

              – aditya birthere
              Nov 15 '18 at 7:04












            • You should add explicit waiter before action with element.

              – Oleksii
              Nov 15 '18 at 7:11











            • Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

              – aditya birthere
              Nov 15 '18 at 7:42











            • so, the error is right. Sorry but it is another question.

              – Oleksii
              Nov 15 '18 at 9:35















            0














            Move browser.waitForAngularEnabled(false); to configuration protractor.conf.js file into onPrepare section.



            export let config = 
            ...
            ...
            onPrepare () =>
            browser.waitForAngularEnabled(false);
            ...
            ,
            ...
            ...
            ;


            Or disable wait for angular before browser.get(), then enable after browser.get()



            describe('Login Scenarios', function () 

            it('First IT block', function ()
            // disable if opening page is non-angular page
            browser.waitForAngularEnabled(false);
            browser.get('http:XXXXXXXXXXXXXXXXXXXX');

            // revert back to enable, after the non-angular page opened.
            browser.waitForAngularEnabled(true);

            browser.manage().window().maximize();
            LoginPage.Login(USERNAME, PASSWORD);

            );
            it('Second IT block', function ()
            Properties.logout.click();
            Properties.confirmlogout.click();
            AutomationUtility.hold();
            );
            );





            share|improve this answer

























            • Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

              – aditya birthere
              Nov 14 '18 at 12:55












            • tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

              – aditya birthere
              Nov 15 '18 at 7:04












            • You should add explicit waiter before action with element.

              – Oleksii
              Nov 15 '18 at 7:11











            • Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

              – aditya birthere
              Nov 15 '18 at 7:42











            • so, the error is right. Sorry but it is another question.

              – Oleksii
              Nov 15 '18 at 9:35













            0












            0








            0







            Move browser.waitForAngularEnabled(false); to configuration protractor.conf.js file into onPrepare section.



            export let config = 
            ...
            ...
            onPrepare () =>
            browser.waitForAngularEnabled(false);
            ...
            ,
            ...
            ...
            ;


            Or disable wait for angular before browser.get(), then enable after browser.get()



            describe('Login Scenarios', function () 

            it('First IT block', function ()
            // disable if opening page is non-angular page
            browser.waitForAngularEnabled(false);
            browser.get('http:XXXXXXXXXXXXXXXXXXXX');

            // revert back to enable, after the non-angular page opened.
            browser.waitForAngularEnabled(true);

            browser.manage().window().maximize();
            LoginPage.Login(USERNAME, PASSWORD);

            );
            it('Second IT block', function ()
            Properties.logout.click();
            Properties.confirmlogout.click();
            AutomationUtility.hold();
            );
            );





            share|improve this answer















            Move browser.waitForAngularEnabled(false); to configuration protractor.conf.js file into onPrepare section.



            export let config = 
            ...
            ...
            onPrepare () =>
            browser.waitForAngularEnabled(false);
            ...
            ,
            ...
            ...
            ;


            Or disable wait for angular before browser.get(), then enable after browser.get()



            describe('Login Scenarios', function () 

            it('First IT block', function ()
            // disable if opening page is non-angular page
            browser.waitForAngularEnabled(false);
            browser.get('http:XXXXXXXXXXXXXXXXXXXX');

            // revert back to enable, after the non-angular page opened.
            browser.waitForAngularEnabled(true);

            browser.manage().window().maximize();
            LoginPage.Login(USERNAME, PASSWORD);

            );
            it('Second IT block', function ()
            Properties.logout.click();
            Properties.confirmlogout.click();
            AutomationUtility.hold();
            );
            );






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 14 '18 at 13:44









            yong

            6,3811411




            6,3811411










            answered Nov 14 '18 at 12:17









            OleksiiOleksii

            809920




            809920












            • Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

              – aditya birthere
              Nov 14 '18 at 12:55












            • tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

              – aditya birthere
              Nov 15 '18 at 7:04












            • You should add explicit waiter before action with element.

              – Oleksii
              Nov 15 '18 at 7:11











            • Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

              – aditya birthere
              Nov 15 '18 at 7:42











            • so, the error is right. Sorry but it is another question.

              – Oleksii
              Nov 15 '18 at 9:35

















            • Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

              – aditya birthere
              Nov 14 '18 at 12:55












            • tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

              – aditya birthere
              Nov 15 '18 at 7:04












            • You should add explicit waiter before action with element.

              – Oleksii
              Nov 15 '18 at 7:11











            • Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

              – aditya birthere
              Nov 15 '18 at 7:42











            • so, the error is right. Sorry but it is another question.

              – Oleksii
              Nov 15 '18 at 9:35
















            Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

            – aditya birthere
            Nov 14 '18 at 12:55






            Oleksii, thanks for the response it does resolve the problem but it takes way the prime capability of the protractor, as protractor does not aware when will be Angular is going to be Enabled and thus causes issues like "element not interactable". Which I am faceing right now.

            – aditya birthere
            Nov 14 '18 at 12:55














            tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

            – aditya birthere
            Nov 15 '18 at 7:04






            tried the waitForAngularEnabled:- true/fasle it is not working it('First IT block', function () browser.waitForAngularEnabled(false); .XXXXX browser.waitForAngularEnabled(true); );

            – aditya birthere
            Nov 15 '18 at 7:04














            You should add explicit waiter before action with element.

            – Oleksii
            Nov 15 '18 at 7:11





            You should add explicit waiter before action with element.

            – Oleksii
            Nov 15 '18 at 7:11













            Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

            – aditya birthere
            Nov 15 '18 at 7:42





            Tried explicit wait (browser.sleep(5000) before action with element but getting the same result.

            – aditya birthere
            Nov 15 '18 at 7:42













            so, the error is right. Sorry but it is another question.

            – Oleksii
            Nov 15 '18 at 9:35





            so, the error is right. Sorry but it is another question.

            – Oleksii
            Nov 15 '18 at 9:35













            0














            I am able to resolve by putting URL in onPrepare section. In to configuration protractor.conf.js file:-



            return browser.get('http://XXXXXXXXXXXXXXXXXXXX/login');



            Thus the protractor is not failing when clicked on the login button. Also not getting any Error while waiting for Protractor to sync with the page.






            share|improve this answer





























              0














              I am able to resolve by putting URL in onPrepare section. In to configuration protractor.conf.js file:-



              return browser.get('http://XXXXXXXXXXXXXXXXXXXX/login');



              Thus the protractor is not failing when clicked on the login button. Also not getting any Error while waiting for Protractor to sync with the page.






              share|improve this answer



























                0












                0








                0







                I am able to resolve by putting URL in onPrepare section. In to configuration protractor.conf.js file:-



                return browser.get('http://XXXXXXXXXXXXXXXXXXXX/login');



                Thus the protractor is not failing when clicked on the login button. Also not getting any Error while waiting for Protractor to sync with the page.






                share|improve this answer















                I am able to resolve by putting URL in onPrepare section. In to configuration protractor.conf.js file:-



                return browser.get('http://XXXXXXXXXXXXXXXXXXXX/login');



                Thus the protractor is not failing when clicked on the login button. Also not getting any Error while waiting for Protractor to sync with the page.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 19 '18 at 12:14

























                answered Nov 19 '18 at 11:43









                aditya birthereaditya birthere

                12




                12



























                    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%2f53299589%2fas-soon-as-protractor-execute-first-it-block-gives-an-error-error-while-waitin%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







                    Popular posts from this blog

                    Top Tejano songwriter Luis Silva dead of heart attack at 64

                    政党

                    天津地下鉄3号線