Forum Discussion
Hi Stephane,
One more thing: attached error is a message from TestExecute itself. What is the error posted to the test log? (The contents of both, error message and extended info pane is relevant.)
Hi,
Thank you all for your suggestions.
The Test Execute test item is the full regression pack which takes 2 hour to run, mostly because the scenarios are data driven but it will be impossible for me to put the code on the forum.
I tried to add breakpoints and ran the full regression pack but this did not turn out well.
- The error happened on Scenario 22 but when I run scenario 22 on its own, the test passed.
- I ran the remaining tests where i got the error on scenario 34. I ran 34 and 35 and as expected the tests passed again.
- I checked the logs which does not show anything. I can see only the actions that test complete performed and the logs just stopped there without any error/details.
Any other suggestion I should be considering?
- tristaanogre6 years agoEsteemed Contributor
Are you using a data driver to drive all your scenarios? If so, and it's a CSV driver, you could have connection issues. The JET database engine behind the CSV driver has a maximum of 65 connections it can have open at a time. If it's always failing at certain scenarios, that seems to be where I'd look... make sure that you're closing connections no longer needed, freeing up objects, etc.
- Stephane6 years agoOccasional Contributor
What do you mean by 65 connections? Are you saying that the testcomplete cannot handle reading from 65 CSV files for example? If so, we are ok as I am only reading from one CSV.
The issue is that the tool is not failing at specific scenarios. It is just failing at some random point. When testexecute failed, e.g. scenario 1. I will run it again on test complete, add a breakpoint and test over. The error will not happen again.
- Marsha_R6 years agoChampion Level 3
Microsoft is responsible for Jet, not TC. ;) 65 connections is the max at one time.
Yes you are only using one csv but if you make a connection in your testing loop and don't force close it at the end, then the first connection is still there the next time when you make the second connection and so on. You can pass up 65 really quickly. This could still look random if you have a close in some places and not in others. Make sure you have a close for every open.
Related Content
Recent Discussions
- 2 days agoGane195