Posted on: 2004/12/28 3:11
Re: QA Smoketests
I would like to ad to the list of Marco's
I use some steps as you probably do when I test/debug modules. It's a quick contribution to our smoketest methodology :
Light explanation :
0/ Validate xoops_version file
>> 0a/ Instalation Help / Readme are included etc
1a/ Test module installation
1b/ Test module upgrade (refresh in admin)
1c/ Test update script (i.e no data are lost)
2/ Play with module under debug mode
- Test admin configuration
>> with a scale of user usability eg: 1=Easy 2 =Medium 3=Hard
- Test use of smarty variables
- Test bloc configuration
3/ Validate translation directories
it's a quick list, I know, but it's the "methodology" I usually use... I'm shure you make other/better tests too !
4/ >> Test user interface ( with various Browsers operating systems )
>> XHTML 1.0 Transitional template output
Couple Question for the Module Developers
1 ) Has there been any decision made on the developer side of the CSS issue of each module having seperate Css files which means when " a basic normal user " adds a module they then have to try and find the right file to edit to get colour right .
( my 1 cents worth )
Themes and modules sort of run hand in hand in my mind so realy the impact on themes should be part of the QA .
Maybe we should use a number of standard themes wether they are the ones bundeled with XOOPS package or what the Theme Forge say are up to stardard . Then the resuls incorperated in the certification that the module compatible with X theme's .
With a scale (1)= Compatable (2)= Possible Minor Template or CSS Modification Needed .