Smoketests format/template, can we start with this...
1 installation
1.1 download
-validate url (as proposed by module developer)
-validate user (if url outside xoops.org, should provide a valid common user for QA download?)
-validate zip file download successful
1.2 preparations
-validate zip file decompression
-validate numbers of decompressed folders / files (e.g. php/sql/language files, as proposed by developer)
-validate README file (or install procedures) existence is a must!
-validate module versions
1.3 install
-validate module files upload successful with required access right
-validate installation procedures (or module upgrade) successful
-validate module existence (ie. admin page)
2 module usage
2.1 admin setting
-block
-group
-preference
2.2 base / configuration data
...
2.3 user functions
...
Should we have a list of 'mandatory' QA items first?
Quote:
Dave_L wrote:
I think the first, or one of the first items on the agenda is to devise a format/template for module smoketests.
Ackbarr and Herko have suggested that the Mozilla Smoketests may provide a good starting point.
I've also outlined some ideas in this Roadmap.
One way to start is to draft an example smoketest for one of the most common modules. And then we can discuss it, and make some refinements.