|Anonymous | Login | Signup for a new account||2019-12-13 13:47 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007196||TestLink||Reports||public||2015-07-10 07:08||2015-07-13 13:00|
|Priority||normal||Severity||feature request||Reproducibility||have not tried|
|Fixed in Version|
|Summary||0007196: "Test Report" historic of all builds|
|Description||The actual "Test Report" only reports the results from last build.|
It should be important to have the historic of each TCs, meaning to see the evolution of the TC result within the builds.
- TCE1: Failed Build001
- TCE1: Passed Build002
- TCE2: Passed Build002
- TCE3: Failed Build001
- TCE3: Failed Build002
- TCE3: Passed Build003
With all information option (e.g: Notes etc.)
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
|Attached Files|| Capture1 (1).GIF [^] (47,675 bytes) 2015-07-10 10:39
|Something similar to ID0001678|
|It would be an historic of all executions on same or different build...but from same Test Plan.|
edited on: 2015-07-10 09:39
>>With all information option (e.g: Notes etc.)
this kind of requirements are useless, nothing can be developed.
>> It would be an historic of all executions on same or different build...but from >>same Test Plan.
ellipis add no value => avoid
A detailed mockup is needed
edited on: 2015-07-10 09:44
>> The actual "Test Report" only reports the results from last build.
have you checked new possibility to have report on SPECIFIC BUILD ?
IMHO if you want to compare things there are other reports that can be used.
Please explore all available reports (It's not clear if you have already done) before reporting
Hello, thanks for your reply.
Yes, I believe I tried all possibilities.
Creating a report for all builds is not a possibility when you have many builds for a specific release.
What I would like is to have an overview of the evolution of all TCs execution for a specific Test Plan.
Otherwise, if you print only the last executions of the TCs (how it is now by default on "Test Report") you don't have the information about the evolution of a TC during the development.
- TCE1: Failed Build001 Notes: Ticket:X
- TCE1: Passed Build002 Notes:
- TCE2: Passed Build002
- TCE3: Failed Build001 Ticket:X
- TCE3: Failed Build002 Ticket:Y
- TCE3: Passed Build003
That would be the result.
your mockup continue to be confusing.
what is TC 3?
hope you can understand that is impossible to do this kind of looping.
>> Yes, I believe I tried all possibilities.
this does not answer my question.
The answer i need is i have tried all available reports.
Because there is already a report that provide you the evolution on different builds providing only exec. result.
IMHO you can use this report as starting point doing customization and giving back to community
TC 1 means -> Test Case ID:1
Yes, I tried all reports.
What I would like is something similar to what was done on Contributions:I0001678 see image
ID1678 is not usable because refers to very old code.
do not think that current structure of test report fits very well.
As stated before
>> Because there is already a report that provide you the evolution on different >> builds providing only exec. result
>> IMHO you can use this report as starting point doing customization and giving >> back to community
I would be glad to do it and give it to the community...
Unfortunately, I do not have the skills.
So if someone knows already how to do it...it would be great.
Thanks anyway fman.
|2015-07-10 07:08||MPRodrigues||New Issue|
|2015-07-10 09:09||MPRodrigues||Note Added: 0023615|
|2015-07-10 09:11||MPRodrigues||Note Added: 0023616|
|2015-07-10 09:38||fman||Note Added: 0023617|
|2015-07-10 09:39||fman||Note Edited: 0023617||View Revisions|
|2015-07-10 09:40||fman||Note View State: 0023617: public|
|2015-07-10 09:41||fman||Note Added: 0023618|
|2015-07-10 09:41||fman||Note Edited: 0023618||View Revisions|
|2015-07-10 09:44||fman||Note Edited: 0023618||View Revisions|
|2015-07-10 09:45||fman||Status||new => feedback|
|2015-07-10 09:55||MPRodrigues||Note Added: 0023619|
|2015-07-10 09:55||MPRodrigues||Status||feedback => new|
|2015-07-10 10:15||fman||Note Added: 0023620|
|2015-07-10 10:21||fman||Assigned To||=> fman|
|2015-07-10 10:21||fman||Status||new => feedback|
|2015-07-10 10:39||MPRodrigues||File Added: Capture1 (1).GIF|
|2015-07-10 10:39||MPRodrigues||Note Added: 0023621|
|2015-07-10 10:39||MPRodrigues||Status||feedback => assigned|
|2015-07-10 12:21||fman||Note Added: 0023622|
|2015-07-10 12:21||fman||Assigned To||fman =>|
|2015-07-10 12:42||MPRodrigues||Note Added: 0023623|
|2015-07-13 11:25||MPRodrigues||Note Added: 0023624|
|2015-07-13 12:59||fman||Note Deleted: 0023624|
|2015-07-13 13:00||fman||Status||assigned => new|
|Copyright © 2000 - 2019 MantisBT Team|