Morph MORPH
SIGN IN SIGN UP
SeleniumHQ / selenium UNCLAIMED

A browser automation framework and ecosystem.

0 0 1304 Java
Normal View History Raw
DanielWagnerHall: s/Conservatory/Conservancy/g r15204
2011-12-16 13:19:25 +00:00
// Copyright 2011 Software Freedom Conservancy. All Rights Reserved.
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
/**
* @fileoverview Contains several classes for handling commands.
*/
goog.provide('webdriver.Command');
goog.provide('webdriver.CommandExecutor');
goog.provide('webdriver.CommandName');
JasonLeyba: Clients that desire only a CommandExecutor should not have to include WebDriverJS' promise management system. Replacing promises in the CommandExecutor with node-style callbacks. Node style, because errors-passed first reminds the user to actually handle the potential error. r14372
2011-10-25 20:29:26 +00:00
goog.provide('webdriver.CommandResponse');
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
/**
* Describes a command to be executed by the WebDriverJS framework.
DanielWagnerHall: Some minor fixes and mime types r16130
2012-03-05 13:18:07 +00:00
* @param {string} name The name of this command.
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
* @constructor
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.Command = function(name) {
/**
* The name of this command.
DanielWagnerHall: Some minor fixes and mime types r16130
2012-03-05 13:18:07 +00:00
* @type {string}
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
* @private
*/
this.name_ = name;
/**
* The parameters to this command.
JasonLeyba: Since an object's keys are always, by definition, strings, there is no need to include this information in jsdoc type annotations. r14353
2011-10-24 21:33:37 +00:00
* @type {!Object.<*>}
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
* @private
*/
this.parameters_ = {};
};
/**
DanielWagnerHall: Some minor fixes and mime types r16130
2012-03-05 13:18:07 +00:00
* @return {string} This command's name.
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.Command.prototype.getName = function() {
return this.name_;
};
/**
* Sets a parameter to send with this command.
* @param {string} name The parameter name.
* @param {*} value The parameter value.
* @return {!webdriver.Command} A self reference.
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.Command.prototype.setParameter = function(name, value) {
this.parameters_[name] = value;
return this;
};
/**
* Sets the parameters for this command.
JasonLeyba: Since an object's keys are always, by definition, strings, there is no need to include this information in jsdoc type annotations. r14353
2011-10-24 21:33:37 +00:00
* @param {!Object.<*>} parameters The command parameters.
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
* @return {!webdriver.Command} A self reference.
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.Command.prototype.setParameters = function(parameters) {
this.parameters_ = parameters;
return this;
};
/**
* Returns a named command parameter.
* @param {string} key The parameter key to look up.
* @return {*} The parameter value, or undefined if it has not been set.
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.Command.prototype.getParameter = function(key) {
return this.parameters_[key];
};
/**
DanielWagnerHall: Some minor fixes and mime types r16130
2012-03-05 13:18:07 +00:00
* @return {!Object.<*>} The parameters to send with this command.
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.Command.prototype.getParameters = function() {
return this.parameters_;
};
/**
* Enumeration of predefined names command names that all command processors
* will support. Implemented as a map so the enumeration can be properly
* exported as part of WebDriver's public API.
JasonLeyba: Since an object's keys are always, by definition, strings, there is no need to include this information in jsdoc type annotations. r14353
2011-10-24 21:33:37 +00:00
* @type {!Object.<string>}
JasonLeyba: Export the Command and CommandName types as part of the WebDriver module. r15823
2012-02-03 19:10:38 +00:00
* @export
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
// TODO(jleyba): Delete obsolete command names.
webdriver.CommandName = {
'GET_SERVER_STATUS': 'status',
'NEW_SESSION': 'newSession',
JasonLeyba: Creating a front end for the WebDriver server, accessible at http://localhost:4444/wd/hub. r14853
2011-11-23 00:15:00 +00:00
'GET_SESSIONS': 'getSessions',
JasonLeyba: Add temporary support to WebDriverJS for the Firefox DOM executor. r15179
2011-12-13 19:05:32 +00:00
'DESCRIBE_SESSION': 'getSessionCapabilities',
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
'CLOSE': 'close',
'QUIT': 'quit',
'GET_CURRENT_URL': 'getCurrentUrl',
'GET': 'get',
'GO_BACK': 'goBack',
'GO_FORWARD': 'goForward',
'REFRESH': 'refresh',
'ADD_COOKIE': 'addCookie',
'GET_COOKIE': 'getCookie',
'GET_ALL_COOKIES': 'getCookies',
'DELETE_COOKIE': 'deleteCookie',
'DELETE_ALL_COOKIES': 'deleteAllCookies',
JasonLeyba: Add temporary support to WebDriverJS for the Firefox DOM executor. r15179
2011-12-13 19:05:32 +00:00
'GET_ACTIVE_ELEMENT': 'getActiveElement',
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
'FIND_ELEMENT': 'findElement',
'FIND_ELEMENTS': 'findElements',
'FIND_CHILD_ELEMENT': 'findChildElement',
'FIND_CHILD_ELEMENTS': 'findChildElements',
'CLEAR_ELEMENT': 'clearElement',
'CLICK_ELEMENT': 'clickElement',
'SEND_KEYS_TO_ELEMENT': 'sendKeysToElement',
'SUBMIT_ELEMENT': 'submitElement',
'TOGGLE_ELEMENT': 'toggleElement',
'GET_CURRENT_WINDOW_HANDLE': 'getCurrentWindowHandle',
'GET_WINDOW_HANDLES': 'getWindowHandles',
'SWITCH_TO_WINDOW': 'switchToWindow',
'SWITCH_TO_FRAME': 'switchToFrame',
'GET_PAGE_SOURCE': 'getPageSource',
'GET_TITLE': 'getTitle',
'EXECUTE_SCRIPT': 'executeScript',
'EXECUTE_ASYNC_SCRIPT': 'executeAsyncScript',
'GET_ELEMENT_TEXT': 'getElementText',
'GET_ELEMENT_TAG_NAME': 'getElementTagName',
'IS_ELEMENT_SELECTED': 'isElementSelected',
'IS_ELEMENT_ENABLED': 'isElementEnabled',
'IS_ELEMENT_DISPLAYED': 'isElementDisplayed',
'GET_ELEMENT_LOCATION': 'getElementLocation',
'GET_ELEMENT_SIZE': 'getElementSize',
'GET_ELEMENT_ATTRIBUTE': 'getElementAttribute',
'GET_ELEMENT_VALUE_OF_CSS_PROPERTY': 'getElementValueOfCssProperty',
'ELEMENT_EQUALS': 'elementEquals',
'SCREENSHOT': 'screenshot',
'DIMISS_ALERT': 'dimissAlert',
'IMPLICITLY_WAIT': 'implicitlyWait',
'SET_SCRIPT_TIMEOUT': 'setScriptTimeout',
'GET_ALERT': 'getAlert',
'ACCEPT_ALERT': 'acceptAlert',
'DISMISS_ALERT': 'dismissAlert',
'GET_ALERT_TEXT': 'getAlertText',
'SET_ALERT_VALUE': 'setAlertValue'
};
JasonLeyba: Clients that desire only a CommandExecutor should not have to include WebDriverJS' promise management system. Replacing promises in the CommandExecutor with node-style callbacks. Node style, because errors-passed first reminds the user to actually handle the potential error. r14372
2011-10-25 20:29:26 +00:00
/**
* Type definition for a WebDriver response object as defined by the wire
* protocol.
* @typedef {{status:bot.ErrorCode, value:*}}
*/
webdriver.CommandResponse;
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
/**
* Handles the execution of {@code webdriver.Command} objects.
* @interface
*/
webdriver.CommandExecutor = function() {};
/**
JasonLeyba: Clients that desire only a CommandExecutor should not have to include WebDriverJS' promise management system. Replacing promises in the CommandExecutor with node-style callbacks. Node style, because errors-passed first reminds the user to actually handle the potential error. r14372
2011-10-25 20:29:26 +00:00
* Executes the given {@code command}. If there is an error executing the
* command, the provided callback will be invoked with the offending error.
* Otherwise, the callback will be invoked with a null Error and non-null
* {@code webdriver.CommandResponse} object.
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
* @param {!webdriver.Command} command The command to execute.
JasonLeyba: Clients that desire only a CommandExecutor should not have to include WebDriverJS' promise management system. Replacing promises in the CommandExecutor with node-style callbacks. Node style, because errors-passed first reminds the user to actually handle the potential error. r14372
2011-10-25 20:29:26 +00:00
* @param {function(Error, !webdriver.CommandResponse=)} callback the function
* to invoke when the command response is ready.
JasonLeyba: The return of the WebDriver JSAPI. This initial version supports Firefox, Chrome, IE, and Opera through the Java Selenium server. For the browsers that support CORS (currently Firefox + webkit), a cross-domain XHR is used to communicate with the WebDriver server. For the other browsers, we have to use JSONP. While IE technically supports CORS, it does not support sending DELETE requests via CORS. Since there are quite a few DELETE commands in the wire protocol, we have to use JSONP for IE too (yay, IE). To create a deployable webdriver.js, run $./go webdriverjs The generated file (build/javascript/webdriver-jsapi/webdriver.js) can be used in either the browser or with node. WebDriverJS may only be used in a browser already under WebDriver's control. Furthermore, the WebDriver server URL and session ID must be passed to the script via the wdurl and wdsid query parameters, respectively. To help with debugging, this change includes a simple Node app: $ ./go webdriverjs build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ java -jar build/java/server/src/org/openqa/selenium/server/server-standalone.jar $ node javascript/webdriver-jsapi/node/demo.js --help To manually run the browser demo tests: $ ./go debug-server $ node javascript/webdriver-jsapi/node/demo.js \ --browser=chrome \ --wdUrl=http://localhost:4444/wd/hub \ --url=http://localhost:2310/javascript/webdriver-jsapi/test/e2e/example_test.html There's still a lot to do: - Fix the :webdriverjs build task - Wiki/design documentation - Improve the debug story (as in, write one) - Write a pure-JS command executor using the atoms. This could theoretically be used to replace Selenium Core - Better Node integration r14327
2011-10-22 01:15:11 +00:00
*/
webdriver.CommandExecutor.prototype.execute = goog.abstractMethod;
Reference in New Issue Copy Permalink