Openbravo Issue Tracking System - QA | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0006153 | QA | Tools - Testlink | public | 2008-11-21 17:07 | 2009-11-03 11:41 |
Reporter | psarobe | ||||
Assigned To | plujan | ||||
Priority | normal | Severity | major | Reproducibility | always |
Status | scheduled | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Summary | 0006153: Add a column to be able to write the environment | ||||
Description | There should be another level below the Build so all the results will depend on the environment and you could analyze each test plan not only on the build but yes in the environment | ||||
Steps To Reproduce | |||||
Proposed Solution | 1. Create a table where all the environment can set up 1.1 Windows/PostgreSQL 1.2 Windows/Oracle 1.3 Linux/Oracle 1.4 Linux/Postgres 2. Create a field when starting the execution for an specific build where you can select the environment (combo box) 3. Create another field where you detail the environment being more specific Then all the report will break under build->environment | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2008-11-21 17:07 | psarobe | New Issue | |||
2008-11-28 18:07 | plujan | Assigned To | => plujan | ||
2009-11-03 11:41 | arunkumar | Status | new => scheduled | ||
2009-11-03 11:41 | arunkumar | fix_in_branch | => pi |
There are no notes attached to this issue. |