[JIRA] (JENKINS-59637) In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)

musarratnawaz09@gmail.com (JIRA)

unread,

Oct 3, 2019, 3:40:10 AM10/3/19

to jenkinsc...@googlegroups.com

Musarrat Nawaz created an issue

Jenkins /

JENKINS-59637

In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)

Issue Type:	Bug
Assignee:	Michael Gärtner
Attachments:	Summary.PNG
Components:	testcomplete11-xunit-plugin
Created:	2019-10-03 07:39
Labels:	test-results
Priority:	Major
Reporter:	Musarrat Nawaz

We have Testcomplete project .

There are more than 265 test items (Testcases).

Divided thir execution test items into two free style jobs. (Json file configuration)

Now on execution of one jobs in results un-executed count is showing the results of all test items that are noty supposed to be part of execution for this particular job.

Aslo count Testcases count and no of failures is also not correct.

This issue is appearing from the day when this un-execute status is added in TestExecution summary.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

musarratnawaz09@gmail.com (JIRA)

unread,

Oct 3, 2019, 3:42:03 AM10/3/19

to jenkinsc...@googlegroups.com

Musarrat Nawaz updated an issue

Jenkins /

JENKINS-59637

In TestComplete TestResults Un executed count is incorrect ( showing count of test items that are not supposed to be part of these results)

Change By:	Musarrat Nawaz

We have Testcomplete project .

There are more than 265 test items (Testcases).

Divided thir there execution test items into two free style jobs. ( execution is handled through Json file configuration)

Now on execution of one jobs in results un-executed count is showing the results of all test items that are noty not supposed to be part of execution for this particular job.

Aslo Also count Testcases count and no of failures is also not correct.

This issue is appearing from the day when this un-execute status is added in TestExecution summary.