ContributionsMost RecentMost LikesSolutionsInformations about libraries the tested Application is using Hi, I was wondering if it is possible for TestLeft to access information about which libraries a process, like a Delphi client, has loaded and/or is using. I know it is possible to get the memory/CPU usage of a process, but what about libraries? It is our own application, so maybe it is possible to make this information visible, even if it is hidden in third-party software? Thanks in advance, Florian Does Testleft ui spy support "back" or "upwards" navigation through objects? Hi, I'm using the TestLeft UI Spy as standalone tool. Quite often I use the three elipses button to navigate "down" into object hierarchy, but I can not seem to find a way to navigate either "up" in the hierarchy level or "back" to the object that was selected before. Sometimes I can use the tree structure on the left for "up" navigation, and sometimes the selected object does have a "parent" field. But e.g. in the case of a TreeView object with items in a tree structure, this does not seem to work...I can use the three ellipses button to navigate "down" the tree (via index of the selected sub TreeViewItem), but this is not shown in the tree structure on the left. Also the TreeViewItems do not feature a "parent" field. So why I find the UI spy really useful for grabbing objects and extracting models, I find navigation within object structure slightly awkward. IIRC, the TestComplete ObjectSpy did offer this feature, so either I fail to spot it in TestLeft, or I might have a wish for a feature. Thanks in advance, Florian how quickly does "waitproperty" react to change in value This is a question about the implementation as well as about experience values from testLeft users: I'm thinking about automating performance tests where I want to measure how long some UI operations need to complete. Let's assume it is as simple that as soon as the OK button's property active becomestrue, the operation is finished. In a functional test,waitproperty often did come in very handy to make sure the OK button is not pressed before it is active. But how reliable wouldwaitproperty be if I want to measure the time until the button becomes active? For example at which interval does waitpropertycheck the object property, and how long does such a check take? Also does it depend on the complexity of the application under test? In general, the response times I measure range from few to several seconds, so some inaccuracy would be ok. Thanks in advance, Florian Running UI tests from team foundation server 2018 I created some UI tests with TestComplete using integration into VS to run them as VS test items. With TFS2015, I did install a VSO agent on a physical server, which started in interactive mode (not as a service) on reboot. My build contained the "Visual Studio Test Agent Deployment" step followed by a "Run Functional Tests" step. Everything was fine. With TFS2018, it's a slightly different VSTS agent, and I want to use the "Visual Studio Test" step. Everything is fine and the tests run as long as I have open desktop connection to the server. However if I reboot the server, and the agent starts on reboot, my tests fail with "Unable to initialize TestComplete" due to the need for an interactive workstation. So I just can't find a way to run the tests from TFS2018 the way they ran from TFS2015. Edit: I already tried starting a batch file as Administrator containing %windir%\System32\tscon.exe XY /dest:console XY being the ID of my current Remote Desktop session,. When I run the tests from VS and than execute this batch file, the tests continue and UI objects are available. However the build steps fails with the same message. Thanks in advance, Florian Re: project cannot be run, because there are no enabled test items that can be run. Thanks both of you. All folders' and test items' checkboxes are checked, in TestComplete and in Visual Studio. As Visual Studio is perfectly able to run tests from projects within same project suite, thesession and active desktop issue doesnot seem the be the problem. I wonder if there is a project-specific TC setting, as even if I clone the project and import it into other project suites, VS gives me the same message. project cannot be run, because there are no enabled test items that can be run. Hi everyone, I have a TestComplete project with several test items, some f them are selectedin theTest Items page of the project editor (especially the top item is, and some directly below). If I right-click the project in the Project Explorer and click "run myProject [Project]", the tests run as desired. In Visual Studio, when I add a "TestComplete 12 test" item and select the project suite containing the project (.pjs file) or the project itself (mds file), the tree structure appears as in the Test Items view, with the same items selected. However, a test run will fail, saying that the "project cannot be run, because there are no enabled test items that can be run. ". Strange thing is that all is perfectly fine for other projects in the same project suite. Thanks in advance, Florian. Re: Unable to initialize TestExecute. Unable to connect to the product. Server execution failed Hi, well, looks like I checked out almost all requirements on the site you linked, resp. another link from there (http://support.smartbear.com/testcomplete/docs/working-with/automating/via-com/configuring-manifests.html): I had setuiAccess="false", but failed to read the line about to "Disable theEnable support for testing Windows Store applicationsoption in TestComplete."..now I disabled it, TestComplete starts and runs the test. Thanks for the link, I might not have looked there again soo soon... Re: Unable to initialize TestExecute. Unable to connect to the product. Server execution failed I'm facing the same message - under certain circumstances: I have VS 2013 andthe VSO agent installed on the test server, as downloaded fromhttp://{your_server}:8080/tfs/_admin/_AgentPool (in TFS 2015). Now there's two scenarios: 1) - I can run the agent using the runAgent.cmd on the test server, (and can even close the RDC windowvia "tscon 1 /dest:console" to keep the user session open (if I just close RDC, GUI tests will fail).). - I start the TFS build - TFS deploys the test agent on the test server - I can start batch scripts from TFS that call msTest.exe on the .tc12Test file I got from integration of TC into VS 2013. - I can also use the build step "visual studio test" to test the .tc12Test assemblies. - The tests run, and produce a .trx file I can use with the TFS extension -> I tend to assume I meet the requirements for running TestComplete tests remotely with Visual Studio Test Agents 2) - I use the task scheduler to call runAgent.com on system start with highest privileges - I reboot the test server - I start the TFS build - TFS deploys the test agent on the test server - upon either running those batch scripts, or the "visual studio test" build step, I will get the message mentionned in the first post. I do not quite understand the difference...and hope to help with the OPs problem. Re: What does TFS build step "Publish TestComplete test results" actually publish Well, sorry, I think I got unprecise towards weekend...yes, I did find the detailed test results, but kind of hidden deeply, and not in a way suitable for extracting daily reports at a glance. By the name of "publish Test Complete results", I just expected, and still would like, to have a TFS build not publish test results where eachTC logFile is counted as one test, but where the TC test cases/items are summed upfrom within the logs (as one logFile documents multiple test cases, since I would not want to start and stop TestComplete between similar testCases at the same GUI element). But technically my question is answered as I now understand what is published, and I will see whether I find a way around it, or ask in the appropriate section if the behavior can be improved. And maybe my approach is not best practice...it's just based on the assumption that starting an application, and than adding an entry, renaming it, and finally deleting it are three testcases, Naturally I would not want to start/close the application between testcases, and it seems awkward to start/stop TestComplete between each such testCase, just that each testVase gets its own logFile. Edit: Also, the log only gets attached for failed runs - if a run succeeds, as I see it, there's no way of telling hom many testCases in it succeeded. Re: What does TFS build step "Publish TestComplete test results" actually publish Update: Now the link "detailed report" leads to a more populated view (Screenshot detailed_2), by double clicking the test run, I can get to the log (Screenshot log). But this still does not allow us to evaluate as I hoped for, since it effectively is counting test runs rather than test cases.