|Anonymous | Login | Signup for a new account||2019-12-14 10:46 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005006||TestLink||Reports||public||2012-05-06 19:54||2012-06-02 10:28|
|Priority||normal||Severity||feature request||Reproducibility||have not tried|
|Product Version||1.9.3 (2011 Q3 - bug fixing)|
|Fixed in Version|
|Summary||0005006: Test Suite Status Report - Execution based stats (FEATURE REQUEST)|
|Description||We are in dire need of a report where we can see the stats based on a build basis for the Test Suites Assigned, This report should show stats from 2 perspective. |
Basically 2 Metrics Table as attached on the defect as an image:
1: Execution Stats for a Build and their stats on Test Suites:
2: Metric of Test Suites execution based upon the Priority of Test Cases executed in a Build.
We need only 2 level of Test Suites from the Root :
Test Suite Root -> Sub Test Suite.
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
|Attached Files|| test suite metrics.jpg [^] (327,633 bytes) 2012-05-06 19:54|
1.png [^] (40,655 bytes) 2012-05-07 03:31
2.png [^] (23,557 bytes) 2012-05-07 03:31
edited on: 2012-05-06 20:06
I forgot to mention that this is per Test Plan report and then the Builds Assigned to that testplan. so if we get a filter for the same before running the report so that its a parameter to report ,it would be great.
This feature is a bit urgent - I do understand that you guys are busy and have loads to do, but if u can prioritize this for an upcoming release like 1.9.4 or a patch I would be really grateful to you guys. You have done an excellent job by building this tool and my company has started to use it very extensively so such reports are being asked by our management for having a tab on the execution status from priority perspective.
I tried creating the SQL but was not able to link the Test Suites with the Test Execution as desired
select NH.id,NH.name,NH_PRJ.id,NH_PRJ.name,NH_TS.id,NH_TS.name from nodes_hierarchy NH
JOIN nodes_hierarchy NH_PRJ ON NH.id = NH_PRJ.parent_id AND NH_PRJ.parent_id = $test_projectId AND NH_PRJ.node_type_id = 2
JOIN nodes_hierarchy NH_TS ON NH_PRJ.id = NH_TS.parent_id AND NH_TS.node_type_id = 2
ORDER BY NH.node_order,NH_PRJ.node_order,NH_TS.node_order;
This query will only display the structure we require but not the status based on execution for the tables in image attached,
1. Unfortunatelly IMHO, requirement has not enough detail to be implemented.
Please write down a complete requirement document with some very detailed example
2. I've already given (I think was to you) this advice: wait till 1.9.4 will be released before doing any kind of try with queries, because we are changing reporting a lot, in order to improve performance and have better control of implementation.
I think anyway you have a option: get code from gitorious report, with special focus on tlTestPlanMetrics.class.php
This is still work in progress but is a lot better as starting point that results.class.php
1. I thought I gave a very detailed image snapshot (attached) on how the report should look like, can you please let me know what more info is required.
2: What is the time frame for release of 1.9.4 ?
I am not good at coding, can do some sql queries though.
Unfortunatelly an image is not a detailed requirement =>
we need a clear written description AND THE IMAGE
For each build ( ? Only active?) the following figures has to be computed in this way ....
>> 2: What is the time frame for release of 1.9.4 ?
July 2012 more or less
edited on: 2012-05-07 19:51
So the intent is to get the stats as shown in the images above with the Input to the report as below:
1:Select Test Plan from a combo box ( All Test Plan should be available)
2:Select Build ( All Builds should be available )
User will pass 1 Test Plan and 1 Build under that test plan as a parameter to this report.
Then we should get the output as Image 1 and 2.
Also the stats are based upon only the assigned test cases in a build. Unassigned Test Cases need not be mentioned in the output.
Did the above explanation suffice from requirement of the feature perspective or in case you think its still not clear then please let me know.
|2012-05-06 19:54||techieguy||New Issue|
|2012-05-06 19:54||techieguy||File Added: test suite metrics.jpg|
|2012-05-06 19:58||techieguy||Note Added: 0016643|
|2012-05-06 20:06||techieguy||Note Edited: 0016643||View Revisions|
|2012-05-06 20:22||techieguy||Note Added: 0016644|
|2012-05-06 20:52||fman||Note Added: 0016645|
|2012-05-07 03:28||techieguy||Note Added: 0016646|
|2012-05-07 03:31||techieguy||File Added: 1.png|
|2012-05-07 03:31||techieguy||File Added: 2.png|
|2012-05-07 07:30||fman||Note Added: 0016650|
|2012-05-07 19:50||techieguy||Note Added: 0016652|
|2012-05-07 19:51||techieguy||Note Edited: 0016652||View Revisions|
|2012-05-12 22:15||techieguy||Note Added: 0016670|
|2012-06-02 10:26||fman||Summary||Test Suite Status Report - Execution based stats => Test Suite Status Report - Execution based stats (FEATURE REQUEST)|
|Copyright © 2000 - 2019 MantisBT Team|