configuration is not working

[calystoramesh]

I am new to angular JS testing , I followed you instruction for setup the protractor with sample. While on execute the testcases I getting a error

C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\bin>protractor e:\protractor_workspace\protractor-master\example\protractorConf.js
Using the selenium server at http://localhost:4444/wd/hub
FF

Failures:

1. angularjs homepage should greet using binding
   Message:
   TypeError: Cannot call method 'get' of undefined
   Stacktrace:

I changed browser name and path only in "protractorConf.js".

capabilities: {
'browserName': 'firefox'
},

// Options to be passed to Jasmine-node.
jasmineNodeOpts: {
// Spec folders are relative to the current working directly when
// protractor is called. This can be folders or files.
specFolders: ['e:/protractor_workspace/protractor-master/example/onProtractor.js'],
isVerbose: false,
showColors: true,
includeStackTrace: true
}
};

let me know I made any mistake ?

[juliemr]

I haven't played with this on Windows yet, so it's possible that this is a windows-specific issue. The changes you made to the configuration file look fine to me. I've pushed a commit that might help with this.

[calystoramesh]

still problem before open the browser . all testcases are trying to execute . then browser opened .. getting error in

timers.js:103
if (!process.listeners('uncaughtException').length) throw e;
^
UnknownError: Bad request

Command duration or timeout: 1.50 seconds
Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'
System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version: '1.7.0_17'
Driver info: org.openqa.selenium.firefox.FirefoxDriver
at new bot.Error (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:108:18)
at Object.bot.response.checkResponse (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\response.js:106:9)
at C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:133:20
at C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\base.js:1112:15
at webdriver.promise.ControlFlow.runInNewFrame_ (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1431:20)
at notify (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:315:12)
at notifyAll (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:284:7)
at fulfill (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:389:7)
at C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:600:51
at C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\http\http.js:96:5
==== async task ====
WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:131:49)
at Function.webdriver.WebDriver.createSession (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:110:30)
at Builder.build (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\node_modules\selenium-webdriver\builder.js:70:22)
at startJasmineTests (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\lib\cli.js:98:45)
at run (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\lib\cli.js:77:5)
at Object. (C:\Documents and Settings\sweet\Application Data\npm\node_modules\protractor\lib\cli.js:156:1)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)

Process finished with exit code 1

added in to following statement in to "onProtractor.js"

describe('angularjs homepage', function() {
this.timeout(80000);
var ptor ;
ptor = protractor.getInstance();

beforeEach(function() {
    ptor.get('../index.html#/form');
});

[juliemr]

I've tried the examples on windows and I can't reproduce your problem - possibly it's related to windows XP?

[juliemr]

Hi,

Closing this as obsolete, please reopen if you're still having issues.

[DOwen55]

Hi,
I'm having the exact same issue as described above. I'm also very new to this framework, but I believe I have everything configured correctly. Running the sample test on Windows 7 (using the following command to start the test process: node lib/cli.js conf.js) and using Chrome I've found that the first test in the suite fails as the browser hosted in selenium is still coming online. Once the browser is up, all subsequent tests run successfully.

The error message provided at the end of the test is: "timeout: timed out after 5000 msec waiting for spec to complete"

Switching the test to IE loads the browser up fast enough to catch the first test and all tests run successfully.

When I tried to apply this to my own project with only the lib_spec file, I found that the entire test ran before the browser could launch (0.07 seconds). The browser does launch a second or so later and looks like it's attempting to display the target app, but selenium shut's it down before the page can be loaded. In this case, the error message is: "TypeError: Cannot call method 'get' of undefined." at line 21, which is:
ptor.get('quizangular/index.html');

The final output on the test is: "3 tests, 3 assertions, 2 failures" so it looks like the first test in the file ran successfully. In this case, switching from Chrome to IE still causes the same delay and test failure.

Please let me know if you need any additional information and thanks for any help you can provide.

[juliemr]

Reopening this issuing and closing #43

For your own project, do you have the following lines?

require('protractor/jasminewd');
ptor = protractor.getInstance();

As for the slowness, sounds like that might just be a webdriver on IE issue. Any idea if this same slowness occurs with a webdriverjs test that doesn't use protractor? e.g. just a file that does

var selenium = require('selenium-webdriver');
var driver = new webdriver.Builder().
      usingServer('http://localhost:4444/wd/hub').
      withCapabilities({
        'browserName': 'chrome',
        'version': '',
        'platform': 'ANY',
        'javascriptEnabled': true
      }).build();
driver.get('<your server>');

[DOwen55]

Hi,
No, I was missing the require and protractor instantiation logic. Thank you. Once I added them to the spec, my tests began to run. However, it is still failing the first test due to a time out.

Note that all this behavior is exhibited using the Chrome driver, not the IE driver. After fixing the file, switching to the IE driver does not exhibit this behavior. All tests from my spec ran successfully!

Here is my spec file:

var protractor = require('../lib/protractor.js');
var util = require('util');
require('../jasminewd');

describe('no ptor at all', function() {
  it('should still do normal tests', function() {
    expect(true).toBe(true);
  });
});

describe('protractor library', function() {
  var ptor = protractor.getInstance();

  it('should wrap webdriver', function() {
    ptor.get('index.html');
    expect(ptor.getTitle()).toEqual('Quiz Angular');
  });

  it('should allow a mix of using protractor and using the driver directly',
    function() {
      ptor.get('index.html');
      expect(ptor.getCurrentUrl()).
          toEqual('http://localhost:8000/quizangular/index.html')

    });
});

The test results are as follows:

F . .
Failures:
1)  no ptor at all should still do normal tests
Message:
    Timeout: timed out after 5000 msec waiting for spec to complete
Stacktrace:
    Undefined
Finished in 10.16 seconds
3 tests, 4 assertions, 1 failure

As for the simple webdriverjs as a spec file, it appears to exhibit the same behavior. I took the sample you provided and loaded it as a spec with no additional tests (though I had to rename the first variable to webdriver). The test completes successfully in 0.001 seconds, and the browser loads immediately after. Was this how you intended me to test it?

Adding the following test logic produces the same behavior:

describe('no ptor at all', function() {
  it('should still do normal tests', function() {
    expect(true).toBe(true);
  });
});

[ToddRB]

I'm having trouble similar to the original issue above.
When I run protractor myConfig.js, it starts up the selenium server, then tries to run my first spec.

require('protractor/jasminewd');
ptor = protractor.getInstance();

My spec has the above lines, but when I call ptor.get('/'), it says 'Cannot call method of 'get' undefined at null.

[juliemr]

I've fixed a couple issues with timeout behavior - any issues remaining after 0.8.0?

[ToddRB]

I can't start my tests with
protractor myConfig.js

I need to run it as
node node_modules\protractor\lib\cli.js myConfig.js.

Then it works.

[juliemr]

I'm going to assume this is a windows issue. Will get my hands on one and do some tests.