Forum Discussion
rrivet
New Contributor
I am also having this same problem, and I am running my tests on a 2nd PC using: TestExecute 10.60.3387.11
The main PC has TestComplete 10.60.3387.7
The issue occurs in both TestComplete and TestExecute.
How did a bug like this make it thru testing at SmartBear?
Any resolution yet?
TanyaYatskovska
10 years agoSmartBear Alumni (Retired)
Hi Rich,
Does the issue persist after applying the patch?
- KristinaA10 years agoOccasional Contributor
Problem is solved on both TC 10.60 and TE 10.60 when patch is applied. It could be included in upgrade script of 10.60 or could be listed as available patch to addressed issue. It would save users and TC support time.
- ChrisPro10 years agoContributor
Where is the patch?
Is it integrated to update?
Related Content
- 6 years ago
Recent Discussions
- 11 hours ago
- 13 hours ago
- 15 hours ago