You need to build Firefox with the JSSh extension enabled. To create the XPI
go to JSSh directory and say make xpi that will generate the XPI. The only
problem with the generated XPI is that its format is compatible with only
Firefox 1.5.x versions. We need to tweak the XPI (nothing but a zip
Hi All,
I would like to monitor the load time of an web page once in a 15 mins
for 2hrs, i should log in a file if the load time of that web page
exceeds 20secs, I tried with following code, but sometimes my page
takes more than 100 secs to load, am getting that message after that
100 sec, It
Hi Angrez,
I'm trying to use the FireWatir for automating on Firefox 3.5 on Mac
OS X Leopard (Intel arch). The JSSh XPI I downloaded for Firefox 3.0
was from
http://wiki.openqa.org/download/attachments/13893658/jssh-20080924-Darwin.xpi.
I tried to unpack the XPI and modify the em:maxVersion
I tried to make the new XPI; but there were no make rules defined in the
client.mk. I tried to modify the debug flag details and it seems to be
working fine now.
I'm able to use them on FireFox 3.5. Could you suggest what are the basic
necessary flags.
thanks,
Hari.
On Mon, Jul 6, 2009 at
First you need to do make xpi in the [build directory]/extensions/jssh
directory. This will create xpi in the following directory:
[build directory]/dist.
I use the following .mozconfig file for building Firefox with JSSh on
windows:
. $topsrcdir/browser/config/mozconfig
mk_add_options
Suggestion: get Hudson CI. put all the code in Hudson, make rake tasks
that you define and allow others to trigger test jobs from Hudson web
interface. Hookup ci_reporter to collect test pass/fail messages.
marekj
Watirloo: Semantic Page Objects in UseCases
http://github.com/marekj/watirloo/
Yes i have tried the things at http://wiki.openqa.org/display/WTR/Pop+Ups.
Although being foolish the thread solution works great.
Thanks for the help.
On Jul 6, 11:14 am, marekj marekj@gmail.com wrote:
Have you perused this:http://wiki.openqa.org/display/WTR/Pop+Ups
Have you looked at
Hi,
Yes, the browser window movements, max, min, restore, bring_to_front
rely on the DOM title.
The way IE behaves is it displays the location in the title bar if
'title' tag is empty or does not exist.
I have the following extension in Watirloo for dealing with windows in my tests
The code
