On Aug 8, 6:10 pm, Maciej Katafiasz <[email protected]> wrote:
> > I would suggest you take a look at #16 and the code that Stephen has
> > written so far and try to complete it. This will make HTML testing much
> > easier for everyone.
>
> Right. I was thinking of creating an API to express symbolically
> things about the HTML we expect, along the lines of Python's/Perl's
> mechanize, but a unification is also an option. I'll have a look.
Although I forgot to add that programmatic browsing also allows us to
test user interaction, which can't be done with HTML unification
alone. That allows testing things such as changing the display mode in
widgets that depend on "before" as much as "after" for correctness.
Cheers,
Maciej
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
