I really like the idea of using TestSwarm because it leverages the
whole community in order to get platform and browser coverage. I'm
sure we can all get into the habit of connecting to TestSwarm
regularly - in fact I know a number of us don't close our browsers so
we'd just need to keep a tab open. :) It seems to me that we would
have less of a maintenance burden when we change our browser support
if we use TestSwarm.
Michelle
On 14-Apr-10, at 11:53 AM, Colin Clark wrote:
So, to the question of test automation, there are some options:
1. The TestSwarm server is now fairly easily installable. It's a set
of PHP scripts and a bit of Apache configuration. We'd each probably
have to consistently keep a browser window or two open to the
TestSwarm server, but it should allow us to automate the tests in a
fairly elegant and distributed way.
2. The Opencast community has done some work with JavaScript test
automation using Maven. They're using a tool called JSTestDriver,
which does include some support for QUnit tests. It is reminiscent
of the distributed features in JSUnit, where there's a server
running on each platform receiving results from the test runner, and
then distributing it back to the machine that initiated the the test
run.
http://code.google.com/p/js-test-driver/
Thoughts?
Colin
---
Colin Clark
Technical Lead, Fluid Project
http://fluidproject.org
------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
