ContributionsMost RecentMost LikesSolutionsRe: Windows 8.1 Modern UI - Testcomplete 10 cant identify any of the UI objectHi Alex, I reinstalled TC per your suggestion. I now see the UI Automation extension listed as installed in TC; however, it still cant see any ui objects in the windows store app. Is there something perhaps the developers should set/turn on/enable so TC can have access to the ui objects?Re: Windows 8.1 Modern UI - Testcomplete 10 cant identify any of the UI objectThank you very much for responding to my query. I took a closer look at the installed extensions in TestComplete. I didnt find any extension with the name: UI Automation Support. I read throught http://support.smartbear.com/viewarticle/62886/ and this talks about that i must have an extension with such name installed. And if it is not available to reinstall testcomplete which i did but didnt work. Testcomplete wont recognize any objects inside the store app (xaml based). I have testcomplete 10.0.531.7 enterprise. Why is UI Automation Support plugin missing? and where can I get it. Re: Windows 8.1 Modern UI - Testcomplete 10 cant identify any of the UI objectAdditional information regarding my test environment. The application is build on .NETCore,Version=v4.5.1 framework. I am not sure this makes any diference to TestComplete but thought of mentioning it.Windows 8.1 Modern UI - Testcomplete 10 cant identify any of the UI objectI have a XAML-based Windows Store application on Windows 8.1 and TestComplete cant identify any of the UI object hence unable to interact with the app. I have read through the Testcomplete online about testing store app. At this moment the app is deployed using the "side loading" technique. Also i have installed testcomplete in program files x86 folder as suggested in the online help. Futheremore, Windows UAC is disabled and I logged on with a user with administrative right. I have contacted SmartBear support but they refered me back to the online help. Any suggestions will be highgly appreciated Re: Is TestComplete ready for Windows 8.1 Metro Apps?Ha Sargei, It is good to know testcomplete will be have the support for windows metro. I look forward to the beta when this comes out. Re: Is TestComplete ready for Windows 8.1 Metro Apps?Thank you for your response. that is too bad you are unable to provide a timeline. I am currently using TestComplete and love it and would hate to replace it by another tool that supports at least android apps. Re: Second popup Validationit looks like a custom controller testcomplete cant access. Have you tried moving the mouse over to the sub menu (by first figuring out the x,y coordinates of the main menu relative to Main window)? Or better yet, do a tab key from the Main menu to the sub menu to get into focus. Once in focus you could use up and down keys to navigate the item you want to select. Is TestComplete ready for Windows 8.1 Metro Apps?Is there a time frame for when Testcomplete will be supporting Windows 8.1 Metro Apps? And follow up question will be if will it support ui automation on Android apps and/or MAC os? Re: How to know from which test an error came from at runtimeYou can create your own library to log messages/errors. For example, Create a script called 'Logger' and a function called ErrorMessage(strMsg, sourceOfError,Priority) { if(!priority) priority = 100; //default value if(priority>300) { throw new error(666,sourceOfError + " says:" + strMsg); } } And from within your test function testMyTestase() { try { //do something if (somethingDidnotwork) { Logger.Error("Oops, better luck next time", testMyTestase,3000) } catch(e) { Log.Error(e.description); //this will print 'testMyTestase says Oops, better luck next time' } finally { //optional - incase you want to clean up } }Re: Surpressing warnings?In the code you can disable the log warning by doing the following: Add the following in the OnStartTest event. Or you can also added before you peform the click: Log.Enabled=false Another method is having OnLogWarning Event and filter those messages out you want to surpress. A better solution i think is to check if the controll is disabled prior performing any action on it. Hope this help.