Difference between revisions of "QATrack Development"
Pereriksson (talk | contribs) (Filled table users, removed field lastlogin) |
|||
(16 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | {{Old|EN}} | ||
+ | [[Category:Outdated]] | ||
+ | ''The QATrack tool is no longer in use.'' | ||
+ | |||
[[Category: Quality Assurance]] | [[Category: Quality Assurance]] | ||
__NOTOC__ | __NOTOC__ | ||
Line 28: | Line 32: | ||
{| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | {| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | ||
|- | |- | ||
− | | bgcolor="#EEEEEE" | '''Section''' || bgcolor="#EEEEEE" | '''When''' || bgcolor="#EEEEEE" | ''' | + | | bgcolor="#EEEEEE" | '''Section''' || bgcolor="#EEEEEE" | '''When''' || bgcolor="#EEEEEE" | '''Target''' |
|- | |- | ||
− | | '''Phase 1''' || | + | | '''Phase 1''' || Development of new Features || |
|- | |- | ||
− | | '''Phase 2''' || | + | | '''Phase 2''' || [[QATrack Testing]] new features || 2007-10-20 .. 2007-11-?? |
|- | |- | ||
− | | '''Phase 3''' || | + | | '''Phase 3''' || Bugfixing || |
|- | |- | ||
− | | '''Phase 4''' || | + | | '''Phase 4''' || Community Test / production use || |
|- | |- | ||
|} | |} | ||
Line 81: | Line 85: | ||
|- | |- | ||
| '''User Preferences''' || List the user's all roles. || pereriksson || 100% | | '''User Preferences''' || List the user's all roles. || pereriksson || 100% | ||
− | |||
− | |||
|- | |- | ||
| '''Localization''' || A user should be able to select a User Interface language, which should be stored in the user's profile. || pereriksson || 100% | | '''Localization''' || A user should be able to select a User Interface language, which should be stored in the user's profile. || pereriksson || 100% | ||
Line 94: | Line 96: | ||
| '''Authentication''' || Replace current authentication with CollabNet integration solution. || pereriksson || 85% | | '''Authentication''' || Replace current authentication with CollabNet integration solution. || pereriksson || 85% | ||
|- | |- | ||
− | | '''Users''' || New users should be added to the database. || pereriksson || | + | | '''Users''' || New users should be added to the database. || pereriksson || 100% |
|- | |- | ||
| '''Languages''' || Languages should be manageable by users with the global role "ADM". || pereriksson || 100% | | '''Languages''' || Languages should be manageable by users with the global role "ADM". || pereriksson || 100% | ||
Line 122: | Line 124: | ||
| bundle || varchar(255) || | | bundle || varchar(255) || | ||
|- | |- | ||
− | | available || | + | | available || date || |
|- | |- | ||
| status || VARCHAR(32) || | | status || VARCHAR(32) || | ||
|- | |- | ||
− | | since || | + | | since || date || |
|- | |- | ||
− | | until || | + | | until || date || |
|- | |- | ||
− | | responsible || varchar(255) || | + | | responsible || varchar(99) || |
+ | |- | ||
+ | | tcm_report_uri || varchar(255) || | ||
|} | |} | ||
Line 157: | Line 161: | ||
|} | |} | ||
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
==== builds ==== | ==== builds ==== | ||
{| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | {| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | ||
Line 169: | Line 169: | ||
|- | |- | ||
|} | |} | ||
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
==== l10n_languages ==== | ==== l10n_languages ==== | ||
{| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | {| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | ||
Line 193: | Line 189: | ||
|- | |- | ||
|} | |} | ||
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
==== rss ==== | ==== rss ==== | ||
{| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | {| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | ||
Line 205: | Line 197: | ||
|- | |- | ||
|} | |} | ||
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==== users ==== | ==== users ==== | ||
{| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | {| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | ||
Line 218: | Line 204: | ||
| bgcolor="#EEEEEE" | '''Name''' || bgcolor="#EEEEEE" | '''Type''' || bgcolor="#EEEEEE" | '''Index''' | | bgcolor="#EEEEEE" | '''Name''' || bgcolor="#EEEEEE" | '''Type''' || bgcolor="#EEEEEE" | '''Index''' | ||
|- | |- | ||
− | | | + | | login || VARCHAR(99) || PRIMARY |
|- | |- | ||
| realname || VARCHAR(63) | | realname || VARCHAR(63) | ||
Line 231: | Line 217: | ||
==== users_languages ==== | ==== users_languages ==== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | {| border="1" cellpadding="2" cellspacing="0" style="margin-bottom: 10px; border: 1px solid #CCCCCC; border-collapse: collapse;" | ||
|- | |- |
Latest revision as of 12:37, 9 July 2018
| RU = Статья устарела. | UA = Статья устарела. | EN = This article is outdated. | PT = Este artigo está desatualizado. | #default = This article is outdated.
}}{{#if: | |}}
The QATrack tool is no longer in use.
This page describes the development of QATrack 2.0, starting late September 2007.
Background
For the members of the community that are involved in QA to able to set a high quality on it's work, they must have access to high quality, available tools that help them approach individual and collective goals.
Overview
The name of the tool will be QATrack, and will hold version 2.0.
The following people are involed:
Name | Role | OpenOffice.org Account |
Per Eriksson | Lead Developer | pereriksson |
André Schnabel | Mentor | andreschnabel |
Project Start
The project will start at the end of September 2007.
Project End
The project will continue until the product has been tested successfully and been released.
Schedule
Section | When | Target |
Phase 1 | Development of new Features | |
Phase 2 | QATrack Testing new features | 2007-10-20 .. 2007-11-?? |
Phase 3 | Bugfixing | |
Phase 4 | Community Test / production use |
Feedback
We hare interested receiving feedback from the whole community. Power users are a primary group, other comments are greatly appreciated but have to stand aside from wishes from the power users.
Discussion will take place on the dev@qa.openoffice.org mailinglist. IssueZilla might be used to track individual tasks, but the project will always be documented here.
Features
QATrack 2.0 will implement these major features:
Centralized CollabNet Enterprise Edition (CEE) authentication
This will be achieved by a technically reliable method.
The feature will improve security and simplify password management.
Localization Support
This version will have localization support.
Centralized language management
Langauges will be maintainable directly in the interface.
IssueZilla-integration
The web interface will support reading and generating issues.
Improved interface
An improved web interface with simpler navigation and lighter colors.
Improved source code
Improved security and simplified future development with reusable objects and resources
Technical Implementation
Category | Implementation | Who | Completed |
Builds | Introduce a Comments field for greater flexibility and communication between users working with the same build. Especially important with large language builds having many users. | pereriksson | 50% |
Builds | Introduce a TCM Report URL field as requested for QATrack 1.0. | pereriksson | 25% |
Builds | Introduce integration towards IssueZilla. How should this work? | pereriksson | 40% |
User Management | Users should be able to be set as QA-Leads for languages. These users should be able to assign languages to users. | pereriksson | 40% |
User Preferences | List the user's all roles. | pereriksson | 100% |
Localization | A user should be able to select a User Interface language, which should be stored in the user's profile. | pereriksson | 100% |
First Page | Display last 20 messages from RSS feed. | pereriksson | 90% |
First Page | Display messages written by users with ADM role. | pereriksson | 50% |
Messages | Administration of messages. | pereriksson | 0% |
Authentication | Replace current authentication with CollabNet integration solution. | pereriksson | 85% |
Users | New users should be added to the database. | pereriksson | 100% |
Languages | Languages should be manageable by users with the global role "ADM". | pereriksson | 100% |
Database Tables
All tables have character set "utf8_unicode_ci".
builds
Name | Type | Index |
bid | int(8), UNSIGNED | PRIMARY |
uri | varchar(255) | |
version | varchar(255) | |
language | varchar(255) | |
platform | varchar(255) | |
type | varchar(255) | |
package | varchar(255) | |
bundle | varchar(255) | |
available | date | |
status | VARCHAR(32) | |
since | date | |
until | date | |
responsible | varchar(99) | |
tcm_report_uri | varchar(255) |
builds_comments
Name | Type | Index |
bid | int(8), UNSIGNED | INDEX |
ts | datetime | |
text | text |
builds_issues
Name | Type | Index |
bid | int(8), UNSIGNED | INDEX |
iid | int(8) | INDEX |
builds
Name | Type | Index |
l10n_languages
Name | Type | Index |
l10n_messages
Name | Type | Index |
languages
Name | Type | Index |
rss
Name | Type | Index |
users
Name | Type | Index |
login | VARCHAR(99) | PRIMARY |
realname | VARCHAR(63) | |
VARCHAR(63) | ||
role | enum("", "ADM", "BPR") | |
locale | VARCHAR(8) |
users_languages
Name | Type | Index |