RE: [Simpletest-support] Testing forms

[Matt G. <mgr...@ne...>]

Actually, I solved my own problem.  By dumping most of the class variables I
was able to notice that my form appeared only in the open_forms array but
not in closed_forms where the form routines draw from.  Sure enough, someone
had put the </form> tag inside conditional logic.  Once I fixed that,
everything worked fine.  I've been able to make some useful tests by posting
to the action pages and setting all of the variables manually.  I'm pretty
sure now that the actual form test routines are not going to be helpful
anyway due to the amount of javascript involved in our pages.  Perhaps this
is something we want to look at for refactoring but there's just not the
time now :-\

Regardless, thanks for putting out this fine piece of software.  It's been
very useful, on the whole.  I'll let you know if there's any feature that
comes up that would save us (and probably others) a lot of time.

Matt

-----Original Message-----
From: Marcus Baker [mailto:ma...@la...]
Sent: Tuesday, February 17, 2004 7:00 PM
To: mgr...@ne...; simpletest-support
Subject: Re: [Simpletest-support] Testing forms


Hi...

Matt Griffin wrote:
> I'm new to SimpleTest so bear with me.

So am I ;).

 > However, I can't find
> any documentation for these (the link to for mtesting is dead on the
> website) and I'm having some difficulties.

I am actually writing the documentation for this now. It only actually
rolled out in the last Beta, was buggy and has just been heavily
refactored for Beta4.

 > When I call clickSubmit($label)
> I simply remain on the same page.  My thought is that the submit button is
> not being found or addressed properly but I cannot determine why.

Can you mail me the page source?

 > Also, am
> I correct in assuming that the browser object is ignorant of all
javascript?

Absolutely. In fact the HTML parsing is currently pretty limited as
well. This is the main area of effort right now, but even the version
1.0 release will not have JavaScript support. There is a possibility
that a later version will use the HTML Tidy module for the HTML parsing.
With luck someone will write a PHP extension for the Rhino module (the
JavaScript intepreter) and then a solution would at least be possible.
Realistically that would be a year away at least.

The current schedule is Beta4 in a couple of days (no frames support),
version 1.0 in about 6 weeks. Beta4 has all of the basic HTML widgets,
but no browser history list (no back button). This and a few other
niceties should make it into 1.0, but no further core functionality has
been mapped out. Do you have any requests?

I am afraid you are very much in the early adopter camp here :(. You can
probably use the Java HTTPUnit tool to accomplish what you want,
although it's not so easy to use.

>
> Matt Griffin
>

yours, Marcus

p.s. I have CC'd this to you so that you can just reply with the HTML
source file.
--
Marcus Baker, ma...@la..., no...@ap...