зеркало из https://github.com/mono/qa.git
Updated README with some clarifications and how to use Xephyr instead of Xvfb.
This commit is contained in:
Родитель
079ed038d9
Коммит
c990e315d6
28
README
28
README
|
@ -1,4 +1,3 @@
|
|||
|
||||
To run the monotesting framework, it's easiest to have the needed options
|
||||
in a config file. You do not have to create these files however.
|
||||
The framework will allow you to set these options via the command
|
||||
|
@ -37,7 +36,7 @@ logfile = None
|
|||
Setting up the selenium server:
|
||||
|
||||
Download the selenium rc server from http://seleniumhq.org/download/
|
||||
Unzip the file and cd into selenium-remote-control-1.0-beta-2/selenium-server-1.0-beta-2
|
||||
Unzip the file and cd into selenium-remote-control-1.0.3/selenium-server-1.0.3
|
||||
|
||||
Run the selenium server with this command
|
||||
|
||||
|
@ -61,29 +60,36 @@ http://<testserver>.mono.lab.novell.com:8080/selenium-server/core/Blank.html
|
|||
|
||||
|
||||
####################################################################
|
||||
Xvfb
|
||||
Xephyr
|
||||
|
||||
You can tell selenium to use Xvfb when displaying firefox, so you can
|
||||
continue working on your desktop
|
||||
continue working on your desktop
|
||||
|
||||
In on shell, do the this:
|
||||
$ sudo Xvfb -fp /usr/share/fonts/misc -ac -screen 0 1024x1024x24 -nolisten tcp :3
|
||||
#!/bin/sh
|
||||
# Start Xephyr with it's display set to :1
|
||||
export DISPLAY=:0.0
|
||||
Xephyr -screen 1200x900 -ac :1
|
||||
|
||||
Then in another, start selenium
|
||||
|
||||
$ DISPLAY=:3 java -jar selenium-server.jar [OPTIONS]
|
||||
Then in seperate script, start selenium:
|
||||
|
||||
|
||||
#!/bin/sh
|
||||
export DISPLAY=:1
|
||||
cd /path/to/selenium-remote-control-1.0.3/selenium-server-1.0.3
|
||||
java -jar selenium-server.jar -forcedBrowserModeRestofLine *firefox /usr/lib64/firefox/firefox
|
||||
|
||||
##################################################################
|
||||
Design Patterns
|
||||
|
||||
See qa/selenium/xsp1/web_service/test_service/addTest.py for design patterns
|
||||
and naming conventions
|
||||
and naming conventions
|
||||
|
||||
##################################################################
|
||||
Project Rules
|
||||
|
||||
* For every .py, there should be a corresponding .html that contains the selenium
|
||||
IDE importable test case
|
||||
* For every test .py file, there should be a corresponding .html that contains the
|
||||
selenium IDE importable test case
|
||||
* Each .py file in the project (other than the selenium, testopia and empty
|
||||
files), needs to have a vim mode line as the very last line of the file. See
|
||||
qa/selenium/xsp1/web_service/test_service/addTest.py for an example modeline.
|
||||
|
|
Загрузка…
Ссылка в новой задаче