Angular testapp on protractortest.org is broken

[ghost]

Bug report

• Node Version: 7.8.0
• Protractor Version: 5.1.1
• Angular Version: 4.0.1
• Browser(s): Chrome
• Operating System and Version macOs Sierra 10.12.4
• Your protractor configuration file

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

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

exports.config = { allScriptsTimeout: 11000, specs: [ './e2e/*/.e2e-spec.ts' ], capabilities: { 'browserName': 'chrome' }, directConnect: true, baseUrl: 'http://localhost:4200/', framework: 'jasmine', jasmineNodeOpts: { showColors: true, defaultTimeoutInterval: 30000, print: function() {} }, beforeLaunch: function() { require('ts-node').register({ project: 'e2e/tsconfig.e2e.json' }); }, onPrepare() { jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } })); } };

- A relevant example test:
I tested with my own application as wel as with the demo application:

/**

• This is a demo application to demonstrate how to use protractor
• as an end-to-end testing framework. */ import{browser, element, by} from 'protractor'

describe('Protractor Demo App', () => { beforeEach(() => { browser.get('http://www.protractortest.org/testapp/ng2/'); });

it('should have a title', () => {
    expect(browser.getTitle()).toEqual('Test App');
});

});

// protractor imports import{browser, element, by } from 'protractor'

// imports from Page Object import{ HomePage } from './homepage.po'

describe('HomePage tests', () => { /**

• This function contains the testsuite for the tests.

• */

  // homepage for these tests. let page: HomePage;

  beforeEach(() => { //browser.ignoreSynchronization = true; // create the homepage page = new HomePage();

  // navigate the browser to the homepage
  page.navigateToHome();

  });

  it('should have a title', () => { /**

  • Basic check if the page is loaded. */ expect(browser.getTitle()).toEqual(page.pageTitle); });

    - Output from running the test

    1) Protractor Demo App should have a title

    • Failed: Angular could not be found on the page http://www.protractortest.org/testapp/ng2/.If this is not an Angular application, you may need to turn off waiting for Angular. Please see https://github.com/angular/protractor/blob/master/docs/timeouts.md#waiting-for-angular-on-page-load
    • Failed: Error while waiting for Protractor to sync with the page: "window.angular is 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"

    • Steps to reproduce the bug: Create a new project using the latest version of angular/cli and write the basic test. It seems that protractor can't detect the Angular processes. However when turning off the synchronization by using: browser.ignoreSynchronization = true; the tests run without any problem.

So for now, my problem is partially solved by turning off the synchronization. But this can't be the way to continue.

[heathkit]

I think the problem is http://www.protractortest.org/testapp/ng2/ is broken (missing System.js?). We should fix that, but in the meantime you can use https://angularjs.org/ to try an AngularJS app. I'm not aware of a good reference app out there for Angular, but you could run the QuickStart seed.

Leaving this issue open to track the problem with http://www.protractortest.org/testapp/ng2/

[ghost]

When trying with an AngularJS app like https://juliemr.github.io/protractor-demo/ Protractor does it's work. I'll test later today with a fresh Angular project.

[ghost]

I tried again with a fresh Angular project and everything seems to be working fine. I've ported my app in this fresh project and the whole thing breaks again.

I think it has something to do with my application not bootstrapping properly, which would explain why Protractor keeps on waiting for it's bootstrap. But I'm struggling to find a way to see where it is stuck, are there ways to debug this? @heathkit

[ghost]

Okay, following a suggestion, I've added ng-app to the body-tag, which seems to have resolved the issue. I don't think this is the way to go, because it seems quite a hacky way.