Re: QA App?

At 04:05 AM 7/20/00 -0600, Joey Smith wrote:

Some of the stated goals of the QA team: * a simple database application that tracks active QA Team members * team members should be able to administrate their own information * the application should also track available platforms How should we go a/b something like this? I think (for obvious reasons =) that PHP+MySQL would be great. As "qa" and "bugs" are on the same machine, we've got these. Should we write this app. through CVS and when we have a finished product, Sascha or someone will set up the MySQL db? I'm pretty sure the Core guys are not going to be handing out SSH acc'ts or anything...

Here are some notes from an earlier posting to the list. I had started work on the code - however, a paying project came along and interrupted... :) QA Team Manager --------------- The application would be built using PHP and MySQL. (Of course) Here is the initial feature list: - allow testers to enter in basic contact information - allow the testers to change their user details in an password protected area. - allow testers to set their status - they can choose to be listed as:

        - active: meaning that they are eagerly awaiting new tasks :)
        - on call: meaning that are available to accept a task if others are busy or their particular skills are needed
        - inactive: meaning that they are not currently accepting new tasks

- allow developers to view tester information - allow testers to define the platforms that they are testing on. - the tables that support platform information is organized in a simple modular fashion. Each part that makes up a platform (like the OS, server software, php, etc...) is a separate component in the platform_details table. The components in the platform_detail table are organized into a 'platform' in the link_dev_to_platform table. Testers will be able to create multiple platforms.

        This structure, when combined with a few handy editors, should help testers quickly and accurately define their platforms.  This should also cut down the amount of data entry required.  Once someone has entered their platform, it is a simple task to update or change a few details.

        Here are the basic tables that I was planning on using.

create table developer (

        id                              int unsigned not null auto_increment primary key,
        handle                  char (12) not null,
        password                char (12) not null,
        name                    char (64) not null,
        email                   char (255) not null,
        status                  enum ('active','on call','inactive') not null

) create table link_dev_to_platform (

        developer               int unsigned not null primary key,
        group_name              char (12) not null,
        platform_detail int unsigned not null

) create table platform_detail (

        id                      int unsigned not null auto_increment primary key,
        type            enum('Apache Module','Hardware Details','Operating System','Other Software','Perl','PHP','PHP Module','Server') not null,
        name            char(64) not null,
        vartype         char(64) not null,
        version         char(64) not null,
        language        char(64) not null,
        notes           text not null

) Zak Greant Creative Director Nucleus Information Service Inc. "Luck favours the prepared mind" - Louis Pasteur