Well, let's break this down then:
Rajesh2 wrote:
Well, Thank you for the quick response tristaanogre, but we tried the same but it is failing for Desktop application.
For 1, As you said we need to investigate using FindChild and FindAllChildren methods. How do we navigate from child to parent in a desktop application? Could you please give some examples?
The two topics I linked you to in the online help documentation gives examples of how to use those two methods to find child objects. Have you tried using those examples as a starting point? As to your question of "how do we navigate from child to parent in a desktop application"... I'm not sure I understand the question to begin with. Any application, Web or Desktop, has a hierarchy of objects. Sys is the parent object of everything. Process is a method of Sys, that when passed a test string, will return the process object corresponding to the application. e.g., Sys.Process('iexplore') will give you the Windows Internet Explorer process. If your application runs as 'myapp', than Sys.Process('myapp') is your application once it's running. Forms, buttons, controls, etc., are all in a hierarchical tree of objects off your application. A form is a child of the application, which itself has child objects of buttons, text fields, and labels. And they, also, may have child objects depending upon how they are constructed. FindChild and FindAllChildren give you the ability that, given any object, you can search the tree of child objects under that object to find a particular object or set of objects for you to work with. I'm not sure if that counts as "navigating" but that's what this means.
Rajesh2 wrote:
"runmode" or "tag names" is nothing but from excel. Crerate a column with name as "runmode" with data as 'Y' or 'N' below that, if you have 100 testcases and you need to run only 60 testcases and ignore 40, then you can use runmode, wherein you give 'Y' to run the testcase and 'N' to ignore the execution for the same.
My confusion was in your assumption that "runmode" and "tag names" are universal concepts in TestComplete. They are not. Your description clarifies: they are columns in an excel spreadsheet that you wish to use to control test execution and flow. To do so, the easiest way is using a DDT.ExcelDriver to read the data and process it, row by row. Please read Using DDT Drivers. It gives examples of how to do so. What you are asking has to do with what you do with the data once you've obtained the driver and started running the loop. Basically, in the loop, you'll employ if/then logic to check the "runmode" column. If it contains a Y, do something and then go to the next row.. If it contains an N, skip everything and go to the next row. Based upon something else you've posted, it seems you may already have a DDT driver running but it is not working well. Could you copy and paste your code that you are executing? That may help us help you better.
Rajesh2 wrote:
For 5, We weren't able to import the packages. Script fails and we get Python Runtime error and the line failing is for importing packages.
What error message are you getting? What does your code look like? What package are you trying to import? Please post example code so that we can help you. Suggestion: create different topics here on the forums for each question so we can track better the conversations.
Rajesh2 wrote:
Identifying the objects, Comparing the excel files, running the script or suite from command prompt..
Concerning identifying objects, we need specifics. What type of application are you testing? What language is it written in? What type of component are you working on? What have you tried already? What errors are you getting with what you tried? Different applications and implementations require different approaches. There are some standard ways of doing things but, without knowing what you're working with, we are only guessing as to how to help you.
As for comparing excel files, there's a great article and script extension for doing so. See https://support.smartbear.com/viewarticle/42199/.
As for running from the command prompt... I've already posted for you a link on the command line options for TestComplete/TestExecute. Have you tried to implement them? If so, what happened? What errors? What worked/didn't work?
We're happy to help, obviously... but we need more information to be able to give you effective help.
And, again, it would be better to create different topics here on the forums for each specific situation. It will help you track the answer and will make things easier for us to help you AND will benefit others by making the specific topics categorized and searchable.