Hi Sands, > Hey Stewart, looks like a good use of tools we already have. So it looks at > first glance like the only trick is to create a QA version, perhaps some > other Components, and write up the scripts related to these? Is there more > that I'm missing? > > On Sep 25, 2010, at 3:50 AM, Stuart Lewis wrote: > >> I've just been looking at the Moodle JIRA site, and how they use it for >> system testing. This looks a good way of specifying tests in a way that >> makes them easy to execute for non-developers, and gives an easy way to >> track if they have passed or not. >> >> - http://tracker.moodle.org/browse/MDLQA/fixforversion/10431
Yes - that what it looks like. It just seems to be a single issue, with lots of dependencies. So as we commit new features, we could open issues for tests that will test our new code (in a completely complimentary way to any lower level junit or integration tests). Hopefully it might draw other people in to using and being happy to interact with JIRA. It also seems to give a nice way of tracking progress for a testathon, and for tracking the actions if any tests fail. It would be interesting to talk to someone at Moodle to find out if they are able to copy the tests in bulk, so that when it comes to testing the next release, they can make a fresh copy of all the test issues. Cheers, Stuart Lewis IT Innovations Analyst and Developer Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: +64 (0)9 373 7599 x81928 ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
