Beruflich Dokumente
Kultur Dokumente
2
Background
3
High-level Architecture
4
A couple of usage statistics…
• Over 10 projects’
automated/continu
ous test systems,
and many
(uncounted)
individual users.
• Gmail tests,
running at 1
thread/test, went
from taking over
40 minutes to 3.5
minutes
5
Experience Report
6
Browser/OS Issues
7
Browser/OS Issues (cont.)
8
Reliability Issues
9
Reliability Issues (cont.)
10
Reliability Issues (more)
11
Scalability Issues
• Session identification
– Current RC code uses a method of identifying sessions that is
based solely on time.
• For our purposes, this was not unique enough.
• Patch to improve uniqueness made, will be given to open
source repository.
• Multiple tests per RC instance
– Unofficial assumption by RC development team that each
session is in an isolated VM.
• We are considering tradeoffs between this model and adding
full support for concurrent tests in one machine.
12
What about Performance?
13
Other contributions…
14
Out-of-scope RC limitations
15
(and now we switch to Jason…)
16
Which is faster? (1 server, sequential tasks)
3
Servers
Time
17
Which is faster? (4 servers, parallel tasks)
3
Servers
Time
18
How do you add more servers?
19
Make computing a true utility (for anyone)
20
Pricing is cheap, but it’s not free.
21
Demo…
22
Questions?
23
Creator of Selenium Driven aka “Remote Control”
24
Thank you, Paul. :-)
25