Contributions
Re: UI Automation if selected, is increasing the GDI objects of AUT
Hi Tanya, Do you mean cloned as duplication of objects in object browser? If yes, as per my observation, its not creating duplicates in object browser. In that case, GDI objects of TestComplete would increase rather than AUT process. And I can see in my task manager window that GDI objects of our AUT process are getting increased. Thanks, Shrirang1.1KViews0likes0CommentsRe: Cannot run particular Project Test Item using commandline TestExecute?
Thanks for the info. It helped a lot!. The commandline works fine after making a minor change. It does not need "/" character before projectitem:name. This needs to be changed from smartbear site documentation as well !! Thanks, Shrirang2.2KViews0likes0CommentsRe: Cannot run particular Project Test Item using commandline TestExecute?
Hi Simon, Here is the command line that fails. ( "C:\Program Files (x86)\SmartBear\TestExecute 9\Bin\TestExecute.exe" "D:\MaxSql_TestAutomation\TestComplete_ForMaxSqlDesktop\trunk\TC_Automation_Project\TC Automation Project\MaxSql-ARRA-Automation.pjs" /r /p:MaxSql-ARRA-Automation /pi:eFiles /e ) "eFiles" is a folder created on Test Items Editor page of Project Properties page. Kindly confirm that we can execute tests in folders on test items page. If yes, how to do it. Thanks, Shrirang2.2KViews0likes0CommentsCannot run particular Project Test Item using commandline TestExecute?
Hi, Why can't we run particular project test item using commandline TestExecute? For Ex- I have created folders for test suites on Projects Test Items page. I want to execute those individual test suites via command line using TestExecute. Although mentioned on page http://support.smartbear.com/viewarticle/26413/?_ga=1.144875186.745138936.1385364668 its not working. Thanks, Shrirang5.7KViews0likes5CommentsRe: Guidelines to improve maintainability and reusability of KDT scripts
Hello Flavio, There is nothing as such rocket science in it. I can tell you some basic steps.. 1) Start creating small KDT scripts like to start with Login. 2) Then start slowly reusing these scripts in another scripts. 3) Build such common scripts that will build a framework for you relevant to the functionality of your product. 4) And then start creating actual test scripts based on test cases available to you. During this phase, keep reviewing your scripts for any optimal use and changes as applicable to your product. You will need to strike a balance between maintaining existing scripts and creating new ones. This should be a good start for you assuming you are clear with basic programming and manual testing concepts. Hope it helps. Thanks, Shrirang2.1KViews0likes0CommentsRe: Param defaults in scripted function for use in keyword test
yes I do agree and recommend this as a new feature. While calling a function having many fields, needs to be passed with values. Its a tedious job and having such feature will reduce the effort several folds. Thanks, Shrirang1.1KViews1like0CommentsRe: NameMapping Template created on one machine is not seen on other TestComplete machine
Anyone faced this issue? I have created template on one client and while sharing the project with another user on other machine, this template is not available and items are not mapped as per this template. btw we share the project using sub-version Tortoise SVN and VisualSVN systems. Thanks, Shrirang933Views0likes0CommentsNameMapping Template created on one machine is not seen on other TestComplete machine
Hi, I am facing this issue. NameMapping Template created on one machine is not seen on other TestComplete machine. Is it bug in TestComplete or some setting that I am missing. Thanks, ShrirangSolved4.1KViews0likes3Comments