forked from bcotton/selenium-grid
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ChangeLog
199 lines (145 loc) · 7.3 KB
/
ChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
=========================
Selenium Grid ChangeLog
=========================
Summary of changes from 1.0.2 to 1.0.3
======================================
* https proxy support for RC via https.proxyHost and
https.proxyPort JVM properties
(http://clearspace.openqa.org/message/54188)
*
Summary of changes from 1.0.2 to 1.0.3 - Nov 27 2008
====================================================
* Fixed the Ruby example to pick the custom RSpec report from the
appropriate selenium-client installation when there are multiple
selenium-client gems installed.
* Moved the Selenium RC server jar to the vendor/ directory
(as opposed to lib/)
Summary of changes from 1.0.1 to 1.0.2 - Oct 23 2008
====================================================
For End Users
-------------
* Support for Selenium RC 1.0-SNAPSHOT
* Support for highly-efficient parallel Safari runs
* Better reporting for Ruby tests, better RSpec integration, and
simplified spec helper, all based on the work that happened
on the selenium-client gem
* DeepTest example for Ruby parallel runs
* Remote Control: allow user to specify a proxy
(http.proxyHost and http.proxyPort system properties)
* Added a restful shutdown for Selenium Grid Hub .
* Less brutal shutdown task for Hub and Remote Controls
(POST /lifecycle-manager action=shutdown)
* Samples now showcasing Flickr as Amazon website is changing way too often
* Rakefile now honors hub port defined in grid_configuration.xml
(Thank you Bob Cotton)
* Bug Fixes
* Improved FAQ and website
For Developers
--------------
* Refactoring of Browser dispatch (simpler)
* Metrics build, PMD and Cobertura reports
* Dryer ant files
* Started work on agent
Thank you:
---------
- Bob Cotton (http://github.com/bcotton) : patch to have the
Rakefile use the hub port defined in grid_configuration.xml
(http://github.com/bcotton/selenium-grid/commits/rakefile_fixes)
Summary of changes from 1.0 to 1.0.1 - Apr 15 2008
==================================================
- Fixed Grid-4 (http://jira.seleniumhq.org/browse/GRID-4):
Selenium does not properly handle accentuated for input fields
- Fixed Grid-6 (http://jira.seleniumhq.org/browse/GRID-6):
Rake task. environments name can't contain space
- Fixed Grid-7 (http://jira.seleniumhq.org/browse/GRID-7):
Selenium Grid does not release a Remote Control when
returned session Id is null
-
Summary of changes from 0.9.4 to 1.0 - Feb 25 2008
===================================================
Main highlights for the 1.0 release include:
Amazon EC2 Integration and Automation
-------------------------------------
Selenium Grid now comes with out-of-the-box support for EC2. There is an
official EC2 image which bundles all the tools you need to establish a
Selenium Grid cluster on Amazon Elastic Compute Cloud (including a VNC
server). Selenium Grid 1.0 also comes with Capistrano tasks to automate
deployment and management of the Selenium Grid on EC2 (in the examples/ec2
directory). Check out the Selenium Grid Website for more details on the EC2
instrumentation and how to run Selenium Grid Demo on EC2.
New Ruby Example
----------------
A new example demonstrating how to run in parallel Selenium tests written in
Ruby (RSpec)
See the examples/rspec directory. The current solution (spawning multiple
processes) is basic but works great and is used daily on professional
projects. The plan is to evolve the current solution to an actual RSpec test
runner based on Rinda/DRb, Memcache or a flavor a MapReduce. Of course
contributions are welcome. Make sure that you also have a look in the
reports directory after running the tests: You will see some nice test
reports including screenshots of the application under test. The screenshot
formatter used in Selenium Grid Ruby example is based on Spec::UI code by
Aslak, just tweaked a little bit to make it work with RSpec 1.1.3.
TestNG based Demo
-----------------
Selenium Grid demo is now powered by TestNG (in lieu of Parallel JUnit)
TestNG provides the best and the more scalable solution to run tests in
parallel for Selenium tests written in Java. The demo now demonstrates best
practices in the field. Feel free to use it as a starting point when
instrumenting your Selenium test suite for Selenium Grid.
RC Startup Parameters
---------------------
Additional parameters can be passed to Selenium remote controls at startup
Just set the seleniumArgs Java property when launching the remote control.
For instance, to start a remote control in multi window and debug mode you
would use:
ant -DseleniumArgs="-multiWindow -debug" launch-remote-control
Ruby dudes can use:
rake hub:start SELENIUM_ARGS="-multiWindow -debug"
Support for Selenium RC 0.9.3
-----------------------------
Selenium Grid now works with 0.9.3 Remote Controls
Just replace the lib/selenium-server-0.9.2.jar library packaged in Selenium
Grid distribution with a 0.9.3 snapshot of Selenium Remote Control if you
want to try it out. Selenium Remote Control 0.9.3 branch changed the way the
session IDs are set and is now using GUIDs.
Better handling of massive text field values
--------------------------------------------
Selenium Grid was choking when testing fields with big chunks of text.
Selenium Grid now uses HTTP POST to relay Selenese commands to the remote
controls and everything works like a charm.
Support for web pages including international characters
--------------------------------------------------------
Selenium Grid was also misbehaving for web pages with international
characters. Not anymore! Selenium Grid now speaks whatever language you
speak. Since Selenium Remote Control does not explicitly set the charset in
HTTP request headers, we changed our HttpClient wrapper to assume UTF-8.
Thanks to Vinay Tota, Maria Elisa Sanchez, Sam Chen, Miles, Shiang Luong,
Daniel Stironek, Adrian Gan, Mattias, Sem Adou, Joel and David Burns for
reporting bugs, suggesting interesting new features or helping me improve
the documentation in the Selenium Grid Forums. Thank you also to Clint
Bishop who helped convert some test to JRuby, and to Patrick Lightbody who
is always here to help me with OpenQA infrastructure.
Summary of changes from 0.9.3 to 0.9.4
======================================
Philippe Hanrigou <http://ph7spot.com>:
* Sample parallel test suite using Ruby/RSpec
* Converted Demo to TestNG
* Made Selenium Grid work with Selenium 0.9.3 RC.
Latest RC has changed the way the session IDs are set and
is now using GUIDs.
* Allow custom arguments to be passed to RCs at startup
ant -DseleniumArgs="..." launch-remote-control
* Bug Fix: Can handle commands with huge text payload.
Use POST not GET to transfer commands to RCs to be able
to process type commands with a huge text
* Bug Fix: Properly handle international characters.
Fixed HttpClient wrapper to assume UTF-8 as Charset is
not explicitely set.
* Introduced JRuby for testing
Clinton Bishop:
* Helped converting some tests to JRuby
Summary of changes from 0.9.2 to 0.9.3 - Nov 22 2007
====================================================
First Release 0.9.2 - Oct 28 2007
=================================