431523 - Run Completion Report incorrectly shows 0 Bugs Found

Status: RESOLVED INVALID

(Testopia :: Reports, defect)

Description

[Mike]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080416 Fedora/2.0.0.14-1.fc8 Firefox/2.0.0.14
Build Identifier: 2-RC1

Run Completion Report for a Test Run with two test cases, one passed one failed, each with a bug attached reports 0 Bugs Found.

Reproducible: Always

Steps to Reproduce:
1. Create a Test Run with two test cases
2. Mark the first test case failed
3. Attach a bug to the first test case
4. Mark the second test case passed
5. Attach a bug to the second test case (enhancement request)
6. From the Test Runs tab right click the run and select Reports > New Run Completion

Observer results on the Dashboard tab.
Actual Results:  
Report shows 1 passed, 1 failed, 0 Bugs Found

Expected Results:  
1 passed, 1 failed, 2 Bugs Found (maybe 1 bug found since only one test case failed, even though each case has a bug attached?)

Bugzilla 3.0.3 and Testopia2-RC1

Comment 1

[Mike]

Attachment: Screenshot of Run Completion and New Bug Report for same Test Run

Notice the two bugs for the test run, but that the run completion report does not reflect the bugs found.

Comment 2

[Ryan Castro]

This appears to be affecting me as well.

Comment 3

[Eugene Sajine]

I noticed the same behavior. I also noticed that if the bug is attached from the test case window>bugs tab then it is not showing properly in the completion report and also this bug doesn't appear in Test Run window > test cases tab in bugs column. As a workaround you need to attach the bug only from  test run window>test cases tab using Bugs tab in test cases details in the bottom.
Then it shows the bug in corresponding column for test case and is able to generate completiong report correctly.
Unfortunately i cannot understand if the fix is already published but i hope the fix will resolve this problem in full.
Please, advise

Comment 4

[Vance Baarda]

(In reply to comment #3)
> I noticed the same behavior.

Which version of Testopia are you running?

Comment 5

[Eugene Sajine]

I'm on version 2.0

Comment 6

[Vance Baarda]

Reopening -- see comment 3.

Comment 7

[Eugene Sajine]

I think i've got the reason of the confusion. The logic seems to be that when you submit the bug from the test case or attach the bug from the test case then this bug cannot be assigned to a particular run, therefore it is not shown in the run and in the run related reports. If you do it from inside the run screen then this entry goes through the all stats for the run and reports.
S it is probably not the bug, but probably a usability issue.

Comment 8

[Greg Hendricks]

(In reply to comment #7)
> I think i've got the reason of the confusion. The logic seems to be that when
> you submit the bug from the test case or attach the bug from the test case then
> this bug cannot be assigned to a particular run, therefore it is not shown in
> the run and in the run related reports. If you do it from inside the run screen
> then this entry goes through the all stats for the run and reports.
> S it is probably not the bug, but probably a usability issue.
> 

This is correct. There has been some (internal) debate about what is the right way to go about this, and this was the compromise that was reached. Runs, only care about bugs that were found in that run, whereas cases can have bugs from the start. There is a separate case bugs report that includes all bugs. For now it will remain as is though.

closing