Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0006153 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [QA] Tools - Testlink | major | always | 2008-11-21 17:07 | 2009-11-03 11:41 | |||||||
Reporter | psarobe | View Status | public | |||||||||
Assigned To | plujan | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | scheduled | Fix in branch | pi | Fixed in SCM revision | ||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
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 | |||||||||||
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 | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
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 |
Copyright © 2000 - 2009 MantisBT Group |