simon_cnhi
Occasional Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Testing MECM (formerly SCCM) console connectivity
Hi all, I have a project suite that is dependent upon Microsoft's Endpoint Configuration Manager console completing connection to the MECM infrastructure in another country. Usually this takes about 30 seconds, however there are times it takes longer and this can abort the whole project suite on the very first step. Is there a way to check, using vbscript, that the console loading process has completed before carrying on with the rest of the test suite? LOADING LOADED ObjectSpy is indicating the different objects between the 2 states, loading & loaded. Loading Aliases.Microsoft_ConfigurationManagement.HwndSource_RibbonConsoleWindow.RibbonConsoleWindow.ConsoleFrame.WPFObject("ConnectingToServer", "", 1).WPFObject("Grid", "", 1) Loaded Aliases.Microsoft_ConfigurationManagement.HwndSource_RibbonConsoleWindow.RibbonConsoleWindow.RibbonConsoleDisplay.WPFObject("HomePageOverview", "", 1) Is there a script method to test for one or the other specific objects? All help truly appreciated. br SimonHistorical posts (pre 2017 so far) no longer link to SmartBear documentation
I'm regularly coming across useful posts by community members, pre 2017 so far, that provide links to SmartBear documentation that would be helpful if only the links work, rather than dumping me on the landing page for "community.smartbear.com". The workaround is to take the exact text from the hyperlink in the legacy post and copy/paste it into the search bar, at which point the original online document/kb article is listed. Example - post title "test complete recognizing unexpected windows", by "chicks" on 09-22-2011, links to SB documentation "OnUnexpectedWindow", but the link does not click through to the documentation. Is it the intention to fix the broken links in the historical posts? cheersAdd a function to duplicate a project suite, and save in different location with a different name
I develop tests for 32bit & 64bit applications. A lot of the keyword tests, between application architectures, are the same, the only difference being steps specific to the 32bit or 64bit features. It's been recommended to develop a separate project suite by using "existing item" for the common keyword tests, and creating specific keyword tests for the different architecture specific features. It seems it is not possible to use "existing item" when referencing a keyword test that launches a "Tested App". It's more preferential to be able to duplicate an entire project suite and customise the required architecture specific keyword tests and keep a distinct project suite for this purpose.Maintain keyword name consistency within a project / project suite
It would be great if TestComplete could automatically maintain keyword test name integrity throughout a project / project suite. I.e., if a keyword test is renamed, the new name is automatically reflected in execution plans and other projects within a project suite when an already defined keyword test is imported into a different project as an "existing item".
