rraghvaniChampion Level 3Joined 3 years ago4351 Posts1214 LikesLikes received528 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsRe: 'ADO' is not defined error - TC v15.79 I'm struggling to replicate what you have provided. I don't know what convertQueryToListOfDictionaries(query) and closeDbConnection(query); is doing. I've made 100 calls to my SQL database to retrieve "Name" from dbo.tbl_Schemes table, by constantly opening, querying and closing without issues. You need to verify that your data is correctly retrieved, and that you are correctly closing the connection. Re: 'ADO' is not defined error - TC v15.79 I don't see ADO usage, in the coding that you have provided? There should be something like, def TestProc(): Cmd = ADO.CreateADOCommand() Cmd.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" + \ 'Data Source=C:\\Users\\Public\\Documents\\TestComplete 14 Samples\\Desktop\\Checkpoints\\XML\\DataGridViewSample\\OrdersDB.mdb' Cmd.CommandText = 'SELECT * FROM orders WHERE orders.[state] = 2' # etc Re: WebModule issues with Virtual Machine Are you able to identify the UI objects shown in https://www.w3schools.com/, and are you able to record simple actions? Does it work? If it's working, then it's most likely relating to your web application. Verify your web application is supported, see Supported Technologies and Applications. If it's not working, then I suggest you get TestComplete installed on your local machine - you can still test your web application using Edge, on your local machine Re: 'ADO' is not defined error - TC v15.79 Are you able to provide example code of it failing? Re: WebModule issues with Virtual Machine Ensure you have SmartBear Test Extension installed and enabled. Ensure you are using 100% DPI settings. Also refer to TestComplete on Virtual Machines Ideally, you should be doing your development work on your local machine, then run the automation on the VM. Re: Unable to Navigate to Code Line from Log Messages I've tested this using TC v15.79.5.7 - clicking on the Warning message in the Log, will navigate to the script file and highlight the code, as shown below. Create a new project, with the above example and see if it works. Otherwise update your TestComplete version, as there's been a number of fixes Re: log message issues in testcomplete I've tested this using TC v15.79.5.7 - clicking on the Warning message in the Log, will navigate to the script file and highlight the code, as shown below. Create a new project, with the above example and see if it works. Otherwise update your TestComplete version, as there's been a number of fixes Re: Storing JUnit XML while the testing is running I'm assuming this is relating to Exporting Test Results? Take note of the following, After each test run, TestComplete generates a test log and stores it to the Log subfolder of your project or project suite folder The file is generated after it's fully completed. Re: TestComplete 15.77 is broken - dont upgrade The latest version of TestComplete comes with Python 3.13. Python has made a number of changes. One of them is treating global as regular scoped objects, which has impacted Python scripts used in TestComplete. See https://support.smartbear.com/testcomplete/docs/scripting/specifics/python_tc_globalobjects.html for more information. You need to update your Python scripts to accommodate this change. It is not recommended to change the Python Interpreter version that comes with TestComplete. Re: TestComplete Closing Issue in Debug Mode What is the difference between this post and Testcomplete closed itself | SmartBear Community ? Are they exactly the same issue? You need to provide more context, as it's not possible to provide a solution based on the information you have given!