|
Size: 1218
Comment:
|
← Revision 11 as of 2007-09-28 12:45:20 ⇥
Size: 1215
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 14: | Line 14: |
| * with the Selenium IDE, a firefox extension [wiki:Self:completesearch/Markus/TestingWithSeleniumRemoteControl/SeleniumIDE [read more]] * with test cases written by you in languages like PHP and using the Selenium (proxy) server (written in Java) [wiki:Self:SeleniumServer [read more]]. |
* with the Selenium IDE, a firefox extension [wiki:Self:completesearch/SeleniumRC/SeleniumIDE [read more]] * with test cases written by you in languages like PHP and using the Selenium (proxy) server (written in Java) [wiki:Self:completesearch/SeleniumRC/SeleniumServer [read more]]. |
Testing with Selenium remote control (short: SeleniumRC)
Homepage: [http://www.openqa.org/selenium-rc/ http://www.openqa.org/selenium-rc/]
"Selenium Remote Control (SRC) is a test tool that allows you to write automated web application UI tests in any programming language against any HTTP website using any mainstream JavaScript-enabled browser. SRC provides a Selenium Server, which can automatically start/stop/control any supported browser. It works by using Selenium Core, a pure-HTML+JS library that performs automated tasks in JavaScript; the Selenium Server communicates directly with the browser using AJAX (XmlHttpRequest)." [from: http://pear.php.net/package/Testing_Selenium]
There are two ways to use SeleniumRC:
with the Selenium IDE, a firefox extension [wiki:completesearch/SeleniumRC/SeleniumIDE [read more]]
with test cases written by you in languages like PHP and using the Selenium (proxy) server (written in Java) [wiki:completesearch/SeleniumRC/SeleniumServer [read more]].
We use a mixture of both ways: writing new tests and debugging is easy with the Selenium IDE. Then we export the test as PHP and integrate the generated code in our test classes.