> ...snip... I've also created another file, SeleniumRunner.js, which
> is supposed to grow into the "test wrapper class" Hugh and I were
> talking about, which will be used through Selenium RC to drive the
> unit tests.
OK, thanks.
I'll be able to start using this when 0.8 comes out and we hav
> I understand. What I wanted to propose is to reuse some of the
> testrunner classes to implement this. I just talked to Thomas and we
> decided to move some of the testrunner classes into the framework. These
> include "testrunner.TestResult", "testrunner.TestCase",
> "testrunner.Suite".
T
Hugh Gibson schrieb:
>> First of all the testrunner is not limited to use just the GUI
>> application it is possible to implement completely independent
>> testrunners. We already have one very simple testrunner called
>> BasicRunner. You can try it by commenting in line 73 and comment
>> out l
> First of all the testrunner is not limited to use just the GUI
> application it is possible to implement completely independent
> testrunners. We already have one very simple testrunner called
> BasicRunner. You can try it by commenting in line 73 and comment
> out line 71 in "testrunner.runn
Hi Hugh,
I have not followed this thread completely but I think I can add a few
words to the testrunner application.
First of all the testrunner is not limited to use just the GUI
application it is possible to implement completely independent
testrunners. We already have one very simple testru
> > JSUnit relies on exceptions for problem reporting but if
> > everything goes through OK it just returns. I'm not sure why the
> > same technique can't be used by the Selenium test layer so that
> > any failure exceptions are caught and documented as failures in
> > the return information.
>
>
> JSUnit relies on exceptions for problem reporting but if everything goes
> through OK it just returns. I'm not sure why the same technique can't be
> used by the Selenium test layer so that any failure exceptions are caught
> and documented as failures in the return information.
Oh yes, that's
> Hm, as we already stated this is significantly different from the
> JSUnit protocol for tests, which relies on exceptions. Which means
> you cannot immedately use the TestLoader.js et al. code from the
> Testrunner for the test wrapper layer (although it would make for a
> good starting point).
Hugh,
> Sorry about the delay in replying.
No bother. I still have an even older post of yours on my todo list.
> Either calling individual tests or using a runAll() function as you
> suggested below. runAll() could take a spec for the functions to test,
> maybe as a regular expression and any f
Thomas,
Sorry about the delay in replying.
> Look, I'm not talking TestRunner right now, not even qooxdoo. I was
> refering to the Selenium log, which you have mentioned as well. All
> I want to get is a clear picture how you envision that a Selenium
> client driver script (think: Python) inte
Hugh Gibson wrote:
>> That means
>> Selenium takes more and more the part of sort of an RPC
>> infrastructure, and is rather concerned with passing values to and
>> fro, but with little logic involved. Am I getting you right so far?
>>
>
> Yes, I suppose so.
>
> I would want to be able to i
Hugh Gibson wrote:
>> I presume you are also not very interested in the Selenium log, when
>> you can have all the evaluation (and therefore logging) in the
>> client driver, right?!
>>
>
> Actually, the client log isn't particularly good at the moment in
> TestRunner. In IE a popup is used
> And I would want all the log output to be in one place. Ultimately
> we would want to capture the complete log including black box tests,
> unit tests and white box tests and automatically email it to relevant
> parties. We do that at the moment for Python unit tests, picking out
> functions
> That means
> Selenium takes more and more the part of sort of an RPC
> infrastructure, and is rather concerned with passing values to and
> fro, but with little logic involved. Am I getting you right so far?
Yes, I suppose so.
I would want to be able to invoke individual tests in Selenium as
> I presume you are also not very interested in the Selenium log, when
> you can have all the evaluation (and therefore logging) in the
> client driver, right?!
Actually, the client log isn't particularly good at the moment in
TestRunner. In IE a popup is used (which has security problems when
r
> Yes. Remote HTTP requests from Javascript were an aside until people
> realised how powerful they were :-)
>
Ok, I get it ... :).
> Selenium is about automating testing of an application, most of which is
> Javascript. Ultimately that javascript has a result in that tags and
> images and wi
> If the test runner tests were incorporated in a "make source" build
> (perhaps with "make source-test") then we could invoke them from a
> source version using injected code from Selenium; alternatively if
> they were included in a "make build-test" version as well then we
> could test the build
Thomas,
> > I would prefer that the output is not through divs but is returned
> > directly to Selenium as strings.
> >
> A quick reply to this detail: Your understanding of Selenium might
> be ahead of mine, but I thought the primary focus of Selenium was
> interacting with the DOM. You usua
Hugh,
> I would prefer that the output is not through divs but is returned
> directly to Selenium as strings.
>
A quick reply to this detail: Your understanding of Selenium might be
ahead of mine, but I thought the primary focus of Selenium was
interacting with the DOM. You usually trigger som
Thomas,
> > I've been thinking about the way we could use Selenium to run
> > unit tests,automating the whole process. The testRunner app is
> > great but it has to be run manually.
> >
> But in general, this could be exactly the app you drive through
> Selenium. Would be a matter of "clickin
Hugh,
> Having now got Selenium running I'm looking at some unit testing stuff.
>
> I've looked at the test runner at
> http://qooxdoo.org/documentation/0.7/frame_apps_testrunner which seems
> quite good.
>
> There are one or two problems which I've reported (issue 821, 822)
>
Yep, got them. One
Having now got Selenium running I'm looking at some unit testing stuff.
I've looked at the test runner at
http://qooxdoo.org/documentation/0.7/frame_apps_testrunner which seems
quite good.
There are one or two problems which I've reported (issue 821, 822)
I've been thinking about the way we cou
22 matches
Mail list logo
