Hey Aron,
You bring up a good point. I'll defer to Justin Obara, Fluid's QA
Lead, to share his thoughts on automated browser testing tools. My
short-form summary is probably this:
Automated acceptance testing is a holy grail we've been questing after
for about three years now. It'll be awesome when we can do it. Biggest
problems: brittleness and "reach." Many scripted acceptance tests tend
to come crashing down when design changes occur because they're tied
to concrete features in the markup such IDs and the like. The reach
issue is simply that it can be hard to automate some tasks that extend
beyond the insides of the browser frame.
Justin can fill you in on the specifics, and where he plans to go from
here on the quest. :)
Hope this helps,
Colin
On 21-Dec-09, at 2:05 PM, Aron Roberts wrote:
On Mon, Dec 21, 2009 at 10:08 AM, Colin Clark
<[email protected]> wrote:
To avoid future confusion, I've drafted a super-simple browser
support chart
for CollectionSpace, intended to keep testing as easy as possible.
When we
have a QA person involved in the community, we can revise this list
and
extend it as needed.
http://wiki.collectionspace.org/display/collectionspace/Browser+Support
Thanks, Colin.
On a related topic, at some point there may be a need to look at
tools for automated testing of the CollectionSpace system through the
browser. Open source examples of these tools include the likes of
Canoo WebTest, Selenium, Sahi et al.; there are apparently commercial
counterparts as well. A couple of starting point links:
http://delicious.com/aronr/web+testing
What have been the Fluid team's experiences with this? At a quick
glance at the Fluid wiki, I see user testing-related pages but not
automated testing-related pages - might there be something relevant
elsewhere on the wiki, or in other documents or maillist archives,
etc.?
Aron
---
Colin Clark
Technical Lead, Fluid Project
http://fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
