Cannot read property '$$testability' of undefined #4233

heathkit · 2017-04-17T19:01:57Z

In Protractor 5.1.1 if your Angular app has a root element other than <body>, you'll see the error Cannot read property '$$testability' of undefined. This is because browser.angularAppRoot() is expected to return the current value of app root if a value isn't passed to it, but currently returns undefined.

The text was updated successfully, but these errors were encountered:

By default, it wasn't returning anything. Now it returns a promise that resolves to internalAngularAppRoot. Fixes angular#4233

By default, it wasn't returning anything. Now it returns a promise that resolves to internalAngularAppRoot. Fixes #4233

SrWildman · 2017-04-27T13:12:10Z

Do we have an ETA on when this will be pushed into the npm package for an easy npm update?

keithrz · 2017-04-27T22:10:07Z

ooohhhhh....that's why I can't create an issue using the protractor test app (v1 angular)! Because the test app has the ng-app attribute on the html element.

http://www.protractortest.org/testapp/ng1/#/form

I'd think you could add some regression tests in the protractor suite against protractortest.org website, to help avoid issues like these in the future. Good luck!

+1 on getting a 5.1.2 release (so that we can create more issues for you to review! Thanks Protractor team, you're doing a great job!!!!)

SrWildman · 2017-05-08T12:58:28Z

Is there any update on implementing this into the next version? Or at least a fix we can make on our end while we wait for it to be pushed?

heathkit · 2017-05-08T18:20:21Z

We're planning to do a 5.1.2 tomorrow that should include this fix.

SrWildman · 2017-05-08T18:50:46Z

@heathkit Thank you very much!!

avinashs15 · 2017-05-15T07:52:15Z

When is the release of 5.1.2 and why is this issue closed. I keep getting this error all the time.. :(
Can the contributor kindly look into this?

benharold · 2017-05-15T21:10:18Z

@avinashs15 You can build from source by following these directions. After you run npm install you'll have a binary at bin/protractor that will work with non-body-tag-based AngularJS apps.

heathkit · 2017-06-02T23:06:13Z

If anyone is still seeing this issue in 5.1.2, could you please reopen with an example that reproduces the problem? Thanks.

tarunkumbnani · 2017-06-14T10:59:55Z

Hi Contributors,

Any updates around this issue . Using protractor version 5.1.2 doesn't resolve this issue.
I have test cases suite that run one after the other and it's quite sporadic... sometimes it works and sometimes they fail because of this issue. So, if you try to run say ~ 30 cases together , you will still get this issue using 5.1.2.

Thank you for your help.

Red-3 · 2017-06-19T16:45:57Z

Using Protractor 5.1.2 we also have 'Error while waiting for protractor to sync with the page: "Cannot read property $$testability of undefined."'
(We are using ng-upgrade and all our AngularJS tests are now timing out because the inherent wait for Angular seems to be broken.)

heathkit · 2017-06-19T17:21:30Z

For those of you still seeing this problem, please post your Protractor config. I'm specifically interested in whether you set rootElement. A github repo or plunkr that demonstrates the problem would be very helpful.

Red-3 · 2017-06-20T22:11:15Z

Protractor config, as requested:

exports.config = {
    seleniumAddress: 'http://localhost:4444/wd/hub',
    getPageTimeout: 200000,
    allScriptsTimeout: 200000,
    //ng12Hybrid: true,
    rootElement: 'body',
    params: {
        login: {
            url:  'https://localhost:8443/docp/public/LoginContainer.jsp'
        }
    },
    specs: [
       'approveSpec.js'
    ],
    onPrepare: function () {
    },

    multiCapabilities: [
        {
              browserName: 'chrome'
        }
    ]
};

Bootstrapping using upgrade module like this:

import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { UpgradeModule } from '@angular/upgrade/static';

import { AppModule } from './app.module';

angular.element(document).ready(() => {
    platformBrowserDynamic().bootstrapModule(AppModule).then(platformRef => {
        console.log('Bootstrapping hybrid app with Upgrade Module');
        const upgrade = platformRef.injector.get(UpgradeModule) as UpgradeModule;

        upgrade.bootstrap(document.body, ['receipt']);
   });
});

tarunkumbnani · 2017-06-21T13:20:42Z

Hi Contributors,
Posting protractor.config file as requested. Just to mention the root element is body so that is not specified in the protractor conf file explicitly.

const port = process.env.SUB_APP_PORT ? ':' + process.env.SUB_APP_PORT : '';
const baseUrl = `${process.env.SUB_APP_BASE_URL}${port}${process.env.SUB_APP_PATH_PREFIX}/`;

 exports.config = {
   allScriptsTimeout: 11000,
   suites: {
    smoke: ['./e2e/uiSpecs/subscriber-login-spec.ts']
  },
   specs: ['./e2e/uiSpecs/*-spec.ts'],
   capabilities: {
    'browserName': 'chrome',
    'acceptSslCerts': true,
    'chromeOptions': {
      'args': ['no-sandbox']
     }
   },
  directConnect: true,
  baseUrl: baseUrl,
  framework: 'jasmine',
   jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function() {}
   },
  };

Thanks for your help.

chiavegatto · 2017-06-28T19:24:51Z

Using Protractor 5.1.2 i have 'Error while waiting for protractor to sync with the page: "Cannot read property $$testability of undefined."'

justtal · 2017-06-29T09:21:12Z

Also facing the same issue.

benharold · 2017-06-30T01:33:40Z

Those who have responded since this issue has been resolved have either:

Had your rootElement defined as body, in which case you have a different problem.
Had your rootElement undefined, meaning it is defaulting to body, in which case you have a different problem.
Have not provided a config.

This issue was specifically related to $$testability being undefined when the rootElement is not the <body> tag, which has been fixed. It is likely you have a different configuration issue.

tarunkumbnani · 2017-07-03T11:19:36Z

Hi @benharold

Thank you for your response.
Is there any separate thread that is tracking this issue when root element defaults to body ?
I have posted my protractor.config file in the thread above. There isn't anything fancy field in the config file which could make me believe that i have a configuration issue.

Any thoughts ?Thanks again.

benharold · 2017-07-06T19:40:41Z

@tarunkumbnani It looks like this pull request may be related to the issue.

divercraig · 2017-08-01T07:43:33Z

Hi @benharold I'm still experiencing this problem while using protractor@5.1.2.

I have explicitly set the root element in the config and still get the problem. My config is below:

"use strict";
exports.config = {
    allScriptsTimeout: 200000,
    directConnect: true,
    specs: [
        "../flights/**/*.js"
    ],
    rootElement: ".ng-app",

    multiCapabilities: [
        {
            "browserName": "chrome",
            "shardTestFiles": true,
            "maxInstances": 4,
            "commandTimeout": 600,
            "idleTimeout": 500,
            "getPageTimeout": 20000
        }
    ],
    jasmineNodeOpts: {
        defaultTimeoutInterval: 200000,
        print: function() {
        } 
    },
    framework: "jasmine2",
    onPrepare: function() {
        var SpecReporter = require("jasmine-spec-reporter");

        var reporterOptions = {
            displayStacktrace: true, // display stacktrace for each failed assertion
            displayFailuresSummary: true, // display summary of all failures after execution
            displaySuccessfulSpec: true, // display each successful spec
            displayFailedSpec: true, // display each failed spec
            displayPendingSpec: false, // display each pending spec
            displaySpecDuration: false, // display each spec duration
            displaySuiteNumber: false, // display each suite number (hierarchical)
            colors: {
                success: "green",
                failure: "red",
                pending: "cyan"
            },
            prefixes: {
                success: "✓ ",
                failure: "✗ ",
                pending: "- "
            },
            customProcessors: []
        };

        jasmine.getEnv().addReporter(new SpecReporter(reporterOptions));
    }
};

In my suite of 62 tests some pass and some fail. It appears to be random which ones pass and which fail. The error messages are:
Failed: Error while waiting for Protractor to sync with the page: "Cannot read property '$$testability' of undefined"

Any advice?

benharold · 2017-08-01T20:38:40Z

@divercraig I'm guessing that .ng-app is not a valid root element. You likely need something along the lines of div[ng-app]. It needs to be a CSS selector that exactly matches only the root element of your app.

vikerman · 2017-08-03T06:01:36Z

Hi - Is this still an issue for some people?

If you are having issues with Protractor and your hybrid app, can you post the following from Chrome devtools console for your app?

window.getAllAngularTestabilities
window.getAngularTestability
window.angular.version

divercraig · 2017-08-09T11:55:02Z

window.getAllAngularTestabilities
undefined
window.getAngularTestability
undefined
window.angular.version
{full: "1.5.9", major: 1, minor: 5, dot: 9, codeName: "timeturning-lockdown"}

webdeveloperninja · 2017-08-09T13:12:14Z

Running protractor 5.1.2. I am getting error
Error while waiting for Protractor to sync with the page: "Cannot read property '$$testability' of undefined"

// Protractor configuration file, see link for more information
// https://github.com/angular/protractor/blob/master/lib/config.ts

const { SpecReporter } = require('jasmine-spec-reporter');
var TfsReporter = require('jasmine-tfs-reporter');

exports.config = {
    jvmArgs: ["-Dwebdriver.ie.driver=" + __dirname + "\\node_modules\\protractor\\node_modules\\webdriver-manager\\selenium\\IEDriverServer3.4.0.exe"],
    allScriptsTimeout: 300000,
    getPageTimeout: 300000,
    specs: [
        './e2e/**/*.e2e-spec.ts'
    ],
    multiCapabilities: [
        {
             'browserName': 'chrome'
        },
        {
            'browserName': 'internet explorer',
            'version': 11,
            'nativeEvents': true,
            'unexpectedAlertBehaviour': 'accept',
            'enablePersistentHover': false,
            'disable-popup-blocking': true,
            'ignoreZoomSetting': true
        }
    ],
    directConnect: false,
    baseUrl: process.env.BASE_URL,
    framework: 'jasmine',
    jasmineNodeOpts: {
        defaultTimeoutInterval: 300000,
        includeStackTrace: true
    },
    beforeLaunch: function () {

    },
    onPrepare() {
        jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
        browser.ignoreSynchronization = false;
        jasmine.getEnv().addReporter(new TfsReporter());
        require('ts-node').register({
            project: 'e2e/tsconfig.e2e.json'
        });
    },
    useAllAngular2AppRoots: true
};

@divercraig did you resolve the issue?

divercraig · 2017-08-09T14:09:33Z

@webdeveloperninja no I haven't resolved this problem. I'm only seeing it intermittently on my tests which is very annoying

webdeveloperninja · 2017-08-09T14:54:53Z

ha get that. @vikerman I am still struggling with this. bellow are those 3 commands outputs

window.getAllAngularTestabilities()
[t]0: t_callbacks: Array(0)_didWork: false_isZoneStable: true_ngZone: t_pendingCount: 0__proto__: Objectlength: 1__proto__: Array(0)

window.getAngularTestability()
vendor.2553bff….bundle.js:1 Uncaught Error: Could not find testability for element.
    at j.ɵglobal.getAngularTestability (vendor.2553bff….bundle.js:1)
    at <anonymous>:1:8

angular version 4.3.3

wswebcreation · 2017-08-10T19:18:10Z

@webdeveloperninja

Can you provide us with an example project in which you also have the scripts to reproduce this issue? I'm working with Protractor 5.1.2 and Angular 4.x and don't have any problems

PE-test · 2017-08-23T14:40:07Z

Hi there,
I'm also seeing similar issue with in my tests: Error while waiting for Protractor to sync with the page: "Cannot read property '$$testability' of undefined"

protractor version: 5.1.2

Config file:

exports.config = {
  seleniumServerJar: 'seleniumServer/selenium-server-standalone-3.5.0.jar',
  getPageTimeout: 15000,
  allScriptsTimeout: 50000,
  defaultTimeoutInterval: 15000,
  includeStackTrace: true,
  rootElement: 'body',
  framework: 'custom',
  frameworkPath: require.resolve('protractor-cucumber-framework'),
  specs: [
    'Tests/Features/*.feature'
  ],
  cucumberOpts: {
    require: [
      'Tests/Steps/*.js' // accepts a glob
    ],
    format: ['json:reports/results.json', 'pretty'],
    profile: false,
    'no-source': true
  },
  capabilities: {
    'browserName': 'Chrome'/*,
    chromeOptions: {
      args: ["--headless", "--disable-gpu", "--window-size=800x600"]
    }*/
  },
  params:{
    environment: 'test',
    environments:{
      dev:{
        mainPage: 'http://google.com',
        dashboardPage: 'https://angular.io/'
      },
      test:{
        mainPage: 'http://google.com',
        myITpage: 'https://angularjs.org/',
        dashboardPage: 'https://angular.io/'
      },
      prod:{
        mainPage: 'http://google.com',
        myITpage: 'https://angularjs.org/',
        dashboardPage: 'https://angular.io/'
      }
    }
  }
};

window.getAllAngularTestabilities
undefined
window.getAngularTestability
undefined
window.angular.version
{full: "1.6.4", major: 1, minor: 6, dot: 4, codeName: "phenomenal-footnote"}

Is there anything else I need to provide?

wswebcreation · 2017-08-23T19:39:32Z

@PE-test

You are using rootElement: 'body' in your config. I thought that wasn't needed when you use AngularJS. Can you please remove it and check again?

PE-test · 2017-08-24T06:51:50Z

@wswebcreation, I'm getting the same error with removed rootElement: 'body'.

wswebcreation · 2017-08-24T07:04:15Z

@PE-test
Can you past a demo project with your config and specs? The pages you mention in your config are no-angular, angularJS and angular. Which one is failing?

PE-test · 2017-08-24T07:37:17Z

@wswebcreation, it is failing on https://angularjs.org/, when trying to get the page for the second time.
You can find project here.

wswebcreation · 2017-08-24T07:51:02Z

@PE-test

Tnx, Will check it later today. What's the command you use to run Protractor in this project

PE-test · 2017-08-24T07:57:31Z

@wswebcreation
protractor conf.js
Plus you may need to add selenium server standalone (please check conf.js).

wswebcreation · 2017-08-24T21:24:17Z

@PE-test

Got half of it working on my machine (Mac OSX 10.12.6) but my internet connection is not that good (not at home). Will take look at it again next week when I'm home. The first tests, on the angularJS site works.

Only difference what I can see now (not that it is the core of the problem) is that I have Protractor as a project dependency and based on your provided project it is a global dependency.

wswebcreation · 2017-08-27T06:15:25Z

@PE-test

There are a few errors in your script. You log and return promises before they are resolved, and there are some undefined errors in your script.

Example:
In your angularJS.js-PO, this breaks, see the comments

  getPlaceholderText: function(){
    var angular = this.angularHomepage;
    var placeholderText;
    // angular.inputField => is undefined
    angular.inputField.getAttribute('placeholder').then(function (placeholder){
      placeholderText = placeholder;
    });
    console.log("Debug: "+placeholderText);
    // Already returned before the Promise is resolved
    return placeholderText;
  }

I get the error you have with Error while waiting for Protractor to sync with the page: "Cannot read property '$$testability' of undefined", but when I run the tests 1 by one there is not issue.
My guess is that your script is causing the errors, and would advice you to recheck and fix all the errors in your script. Start at the beginning and first place all the code you have in in your steps files and remove the usage of the PO's, because there the most errors are.
I don't have enough time to debug the complete script but I hope it helps you

peterpoe · 2017-09-04T10:24:42Z

Hi, having the same problem with version 5.1.2. My config:

exports.config = {
  specs: [
    './scenarios/**/*'
  ],
  capabilities: {
    'browserName': 'chrome'
  },
  baseUrl: 'http://127.0.0.1:8080',
  framework: 'jasmine',
  directConnect: true
};

I found that changing specs to single files instead of a glob, the error goes away:

  specs: [
    './scenarios/spec1.js',
    './scenarios/spec2.js'
  ],

Hope this helps!

victor-geere · 2017-09-06T12:32:23Z

I had to add the following code to get rid of

Error: Error while waiting for Protractor to sync with the page: "window.angular is undefined.

browser.ignoreSynchronization = true;
browser.waitForAngular();
browser.sleep(500);
browser.ignoreSynchronization = false;

then had to increase browser.sleep

browser.sleep(5000);

in order to fix

"Cannot read property '$$testability' of undefined"

So it seems like Angular isn't initialised properly yet

CrReddy846 · 2017-09-20T11:28:35Z

Facing the issue with version 5.1.2

Here is my config File:

exports.config = {
framework: 'jasmine',
rootElement: 'body',

seleniumAddress: 'http://localhost:4444/wd/hub',

specs: ['test_protractor3.js'],
jasmineNodeOpts: {
defaultTimeoutInterval: 500000
}
};

gourishankarmuvvala · 2017-11-30T05:32:37Z

Hi All,
Am using protractor 5.1.2 version, bit still getting the error ** Failed: Error while waiting for Protractor to sync with the page: "Cannot read property '$$testability' of undefined"**. Could any one please let me know how to reslve. My Config is very simple and basic .

uLucasFraga · 2018-07-16T00:28:20Z

Hey, how to solve this problem?
Thx!

ahmetya · 2018-09-24T07:36:45Z

We are experiencing similar kind of problems that we think they are related with testability api.

In previous version of our app, for the elements in pages it is like;
window.getAngularTestability(document.querySelector('#name')).isStable();
true

But after latest versions we are getting a "false" for the method above and protractor somehow lose the interactions with objects.

We can operate on pages via using "browser.ignoreSynchronization = true;" on those pages. But we dont want to use this because of it is aganist control flow and async approach. So we try to figure out which changes one test enviroment result to this.

If you have any idea i glad to hear. Thanks in advance.

Muhammad-Hassan366 · 2019-08-16T11:39:55Z

some times i am facing error of 'cannot read property click of undefined' while executing protractor scripts .can someone please guide that what is the cause of this error?

heathkit added the type: bug label Apr 17, 2017

heathkit self-assigned this Apr 17, 2017

heathkit added a commit to heathkit/protractor that referenced this issue Apr 26, 2017

fix(browser): Fix browser.angularAppRoot()

bede736

By default, it wasn't returning anything. Now it returns a promise that resolves to internalAngularAppRoot. Fixes angular#4233

heathkit mentioned this issue Apr 26, 2017

fix(browser): Fix angularAppRoot() to return a promise #4245

Merged

heathkit closed this as completed in #4245 Apr 26, 2017

heathkit added a commit that referenced this issue Apr 26, 2017

fix(browser): Fix browser.angularAppRoot()

183cd80

By default, it wasn't returning anything. Now it returns a promise that resolves to internalAngularAppRoot. Fixes #4233

keithrz mentioned this issue Apr 28, 2017

Making ElementArrayFinder from an array of ElementFinders #2538

Closed

Shazear mentioned this issue Jul 5, 2017

Fix a problem w/ NG1-2 Hybrid pages bbaia/protractor-net#66

Open

Macstyg mentioned this issue Aug 16, 2017

Failed: unknown error: Cannot read property 'get' of undefined / Angular hybrid JIT #4438

Open

Cannot read property '$$testability' of undefined #4233

Cannot read property '$$testability' of undefined #4233

Comments

heathkit commented Apr 17, 2017 • edited by juliemr Loading

SrWildman commented Apr 27, 2017

keithrz commented Apr 27, 2017

SrWildman commented May 8, 2017

heathkit commented May 8, 2017

SrWildman commented May 8, 2017

avinashs15 commented May 15, 2017

benharold commented May 15, 2017

heathkit commented Jun 2, 2017

tarunkumbnani commented Jun 14, 2017 • edited Loading

Red-3 commented Jun 19, 2017

heathkit commented Jun 19, 2017

Red-3 commented Jun 20, 2017 • edited Loading

tarunkumbnani commented Jun 21, 2017 • edited Loading

chiavegatto commented Jun 28, 2017

justtal commented Jun 29, 2017

benharold commented Jun 30, 2017 • edited Loading

tarunkumbnani commented Jul 3, 2017

benharold commented Jul 6, 2017

divercraig commented Aug 1, 2017 • edited Loading

benharold commented Aug 1, 2017 • edited Loading

vikerman commented Aug 3, 2017

divercraig commented Aug 9, 2017

webdeveloperninja commented Aug 9, 2017 • edited Loading

divercraig commented Aug 9, 2017

webdeveloperninja commented Aug 9, 2017 • edited Loading

wswebcreation commented Aug 10, 2017

PE-test commented Aug 23, 2017 • edited by wswebcreation Loading

wswebcreation commented Aug 23, 2017

PE-test commented Aug 24, 2017

wswebcreation commented Aug 24, 2017

PE-test commented Aug 24, 2017

wswebcreation commented Aug 24, 2017

PE-test commented Aug 24, 2017

wswebcreation commented Aug 24, 2017

wswebcreation commented Aug 27, 2017

peterpoe commented Sep 4, 2017 • edited Loading

victor-geere commented Sep 6, 2017

CrReddy846 commented Sep 20, 2017 • edited Loading

gourishankarmuvvala commented Nov 30, 2017

uLucasFraga commented Jul 16, 2018

ahmetya commented Sep 24, 2018 • edited Loading

Muhammad-Hassan366 commented Aug 16, 2019

heathkit commented Apr 17, 2017 •

edited by juliemr

Loading

tarunkumbnani commented Jun 14, 2017 •

edited

Loading

Red-3 commented Jun 20, 2017 •

edited

Loading

tarunkumbnani commented Jun 21, 2017 •

edited

Loading

benharold commented Jun 30, 2017 •

edited

Loading

divercraig commented Aug 1, 2017 •

edited

Loading

benharold commented Aug 1, 2017 •

edited

Loading

webdeveloperninja commented Aug 9, 2017 •

edited

Loading

webdeveloperninja commented Aug 9, 2017 •

edited

Loading

PE-test commented Aug 23, 2017 •

edited by wswebcreation

Loading

peterpoe commented Sep 4, 2017 •

edited

Loading

CrReddy846 commented Sep 20, 2017 •

edited

Loading

ahmetya commented Sep 24, 2018 •

edited

Loading