Firstly, Hello all,
Just started playing with Selenium, and, just thought I'd mention a few
things that struck me would be nice to have:
1 - Title of current test
I think the titles used should be consistent between the suiteTable row and
the current Test Table. To save me having to write thi
I don't seem to be able to do this in FF
fireEvent
document.getElementById("divA")
mouseover
In IE it works fine. Even the following "bubbles up" fine in IE to the div
(where the mouseover handler resides)
fireEvent
document.getElementById("divA").firstChild
mouseover
but nothing in FF.
Poin
> Selenium
developers don't want such optional statement in selenium
Why? Am I missing something? this isn't
unit testing, it's functional testing...
Sorry, but this is hardly pragmatic - we
need this. If the Selenium developers want to empower us, I'm sure they
could add it. I, for
From:
Médoune
Mbow
Currently I will want to add one or any
actins which will enable me to simulate the loop [for(i=0;i<7;i++)] as in
java, c++, python If somebody has an idea on that which there does
not exist. Or if that were already done I will even like how it is
Hi all,
I'm starting to ramp up my tests/testsuite and have noticed some strange
behaviours in Selenium. Basically, "Access Denied" is returned from some
tests, while others return "Element x not found". Both of these appear
"randomly" - for example, if I repeatedly run and rerun the same tes
fully "ready"... and why it's not working in goBack.
[2] where "never" = thousands of sample runs in my dataset.
- Original Message -
From: "Russ Thomas" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 23, 2005 5:45 PM
Subject: [Selenium-users]
- Original Message -
From: "Mike Williams" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 24, 2005 10:49 AM
Subject: Re: goBack bug? (was Re: [Selenium-users] spurious failures)
There is a race-condition bug in page-reload detection on Firefox, which
I haven't yet been able to get to
- Original Message -
From: "Mike Williams" <[EMAIL PROTECTED]>
All that said: if you can think of a way to do it purely client-side
with JavaScript, that'd be fantastic!
--
Hi Mike
Well, yes and no...
setTimeout (and in some ways setInterval) provide a poor mans version of
threading
Why does this not work in firefox? eg
assertAttribute [EMAIL PROTECTED] myClass
works fine in IE, in FF I see
Actual value 'null' did not match 'myClass'
(I don't know why null is quoted - looks wrong to me).
Anyway, how should attributes be tested in FF? Better, how to do attr
tes
Hi all
Thanks to Mike Williams I think it was, I know I can do
Assert.fail(strMessage);
in user-externsion.js. Question I have now is, how do I do the same
with Verify? Yes, I realise this is an odd thing to want to do -
commands should support assert* and verify* but in this one perculiar
On 12/22/05, Mike Taber <[EMAIL PROTECTED]> wrote:
> So, I'm wondering how others are using this ability to add extensions to
> Selenium?
> Are you not adding much if anything?
Lots!
> Are you just adding general utility type extensions?
Mostly. I've added a few "app specific" things too - but
I really don't understand what you're trying to achieve exactly, but
myiframe.editEvent
should get you closer, if editEvent is in the AUT.
I'm not surprised your first method stops the tests - you've wiped the location.
HTH
Russ
On 12/23/05, Mark Stosberg <[EMAIL PROTECTED]> wrote:
> Hello,
>
12 matches
Mail list logo
