For some reason when I create a regular test list(not the dynamic version) the Tests count is double that of the listed tests in the test list. Is this expected? Am I the only one experiencing this? Is there a way to fix this? I upgraded to the new version and it appears to have the same issue.
6 Answers, 1 is accepted
0
Amy
Top achievements
Rank 2
answered on 09 Jul 2014, 07:19 PM
Never mind I think I figured it out... It appears the tests got added multiple times somehow when I created the list(not sure how this happened)... I think because I selected the folder they were in as well as the tests?
0
Hello,
The numbers should match so there's some bug in this UI. Unfortunately I'm unable to replicate that so any details on how to get there could be of great help for us to isolate and address the problem.
Do you still get the numbers wrong if you reload (close/open) the project?
And no, Test Studio doesn't let you add the same tests in a list multiple times, this is by design.
Regards,
Konstantin Petkov
Telerik
The numbers should match so there's some bug in this UI. Unfortunately I'm unable to replicate that so any details on how to get there could be of great help for us to isolate and address the problem.
Do you still get the numbers wrong if you reload (close/open) the project?
And no, Test Studio doesn't let you add the same tests in a list multiple times, this is by design.
Regards,
Konstantin Petkov
Telerik
0
Amy
Top achievements
Rank 2
answered on 10 Jul 2014, 02:46 PM
It should be noted that I'm using the Internal Build 2014.2.704.0. And no closing and opening the project does not help the numbers. What fixed it was removing the duplicate tests. I have attached screenshots of how I got the duplicate Tests into the Test List. See Before screenshot. After screenshot showing duplicates in the test list and then the just plain duplicatetests that shows me saving the examples in before and after as test to show that is when the numbers get duplicated.
I have also attached the way I fixed this by removing the duplicate tests. See attached removeduplicatetestsbefore, removeduplicatetestsafter, and notduplicated screenshots for the fix.
I have also attached the way I fixed this by removing the duplicate tests. See attached removeduplicatetestsbefore, removeduplicatetestsafter, and notduplicated screenshots for the fix.
0
Hello Amy,
Thanks a lot for all the details/screenshots - that helped me narrow down the problem. I have submitted this bug for our QA and Dev team to look at and address for next version of the product. I have also updated your Telerik points for reporting this problem and helping us improve the product - thank you!
Regards,
Konstantin Petkov
Telerik
Thanks a lot for all the details/screenshots - that helped me narrow down the problem. I have submitted this bug for our QA and Dev team to look at and address for next version of the product. I have also updated your Telerik points for reporting this problem and helping us improve the product - thank you!
Regards,
Konstantin Petkov
Telerik
0
Amy
Top achievements
Rank 2
answered on 11 Jul 2014, 07:56 PM
Great. I'm not sure if this matters, but something else I just remembered in relation to this issue: when the tests get into the testlist multiple times it results in the tests running multiple times as well as the number being duplicated. That is actually what made me realize the tests were in there multiple times.
I've attached 2 screenshots from the results screen. The first one is a test list of ours that had been duplicated showing it's run where it ran duplicates(duplicatetestsran) and then the next run when I figured out to remove the duplicates and successfully got the tests to only run once(withoutduplicatetestsran).
I've attached 2 screenshots from the results screen. The first one is a test list of ours that had been duplicated showing it's run where it ran duplicates(duplicatetestsran) and then the next run when I figured out to remove the duplicates and successfully got the tests to only run once(withoutduplicatetestsran).
0
Hi,
I see. So the problem is more serious than that. We should look into addressing it for next internal and official builds.
Thanks a lot for helping us isolate this problem!
Regards,
Konstantin Petkov
Telerik
I see. So the problem is more serious than that. We should look into addressing it for next internal and official builds.
Thanks a lot for helping us isolate this problem!
Regards,
Konstantin Petkov
Telerik