Command line Execution support for Zephyr Folders
When executing test cases in Test Complete or Test Execute via the command line, you can specify which folder to write the test results to but CAN NOT specificy Zephyr Folder. Please add support for Test Complete/Test Execute to write results to Zephyr Folders via command line (or other executions)1.9KViews3likes3CommentsAdd more log information on Jenkins Smartbear Plugin TestComplete Test Console Output log
Currently there it is just logged with what exe & version & parameters passed. From past experience it would be good to have following details logged too: Configured session details - Run interactive user session flag - Use active session flag - Session screen resolution (sample 2560x1440) The real facts from the Session Desktop during test execution - Is it an interactive user session? - Is an already active session used or did the test runner created a new one? - Session screen resolution (sample 1679x551 which does not match the requested one see above)318Views2likes0CommentsLog Folder Items, Set the Icon while inside the stack (or auto detect on some hiearchy)
I thought this should just be a feature already and I posted asking for help to get it to work. https://community.smartbear.com/t5/TestComplete-General-Discussions/Log-Folder-Icon-Checkpoint-Over-Message-Javascript/m-p/200736#M37434 The log folders are real nice for cleaning up the logs but they only change Icon's if the Folder contains an Error or a Warning. I want LogFolders to show a green if it contains a checkpoint. A common sense order of importance Error > Warning > Checkpoint > Message. Instead it's showing Error > Warning > Message. I think it should even auto detect based on the Log item's priority that has been set. Or just a method to hit ie, Log.CurrentStack(iconWarning, priorityHigh); function TestScriptLog() { Log.AppendFolder("This folder Icon should be an Error"); Log.Message("Informational in Folder","",pmNormal); Log.Checkpoint("Checkpoint in Folder","",pmNormal); Log.Warning("Warning in Folder","",pmNormal); Log.Error("Error in Folder","",pmHighest); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be an Error"); Log.Message("Informational in Folder"); Log.Checkpoint("Checkpoint in Folder"); Log.Warning("Warning in Folder"); Log.Error("Error in Folder"); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be a Warning"); Log.Message("Informational in Folder","",pmNormal); Log.Checkpoint("Checkpoint in Folder","",pmNormal); Log.Warning("Warning in Folder","",pmHighest); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be a Warning"); Log.Message("Informational in Folder"); Log.Checkpoint("Checkpoint in Folder"); Log.Warning("Warning in Folder"); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be a Checkpoint"); Log.Message("Informational in Folder","",pmNormal); Log.Checkpoint("Checkpoint in Folder","",pmHighest); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be a Checkpoint"); Log.Message("Informational in Folder"); Log.Checkpoint("Checkpoint in Folder"); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be an Informational"); Log.Message("Informational in Folder","",pmHighest); Log.PopLogFolder(); Log.AppendFolder("This folder Icon should be an Informational"); Log.Message("Informational in Folder"); Log.PopLogFolder(); }Command line import of TC/TE settings
As someone who is automating the creation of my test environment, I would like to automate the configuration of TestComplete/TestExecute. TestComplete allows for a manual import of a settings file TestExecute does not. This is a problem when I'm attempting to spin up VMs from scratch and immediately start tests. For both products, I would like to be able to use a settings file that I have previously exported to set my desired product settings at the command line either during or after install to finish the product configuration.788Views2likes0CommentsGet and Evaluate Response of Batch-Script as Tested App
In some cases it is useful / necessary to run a batch script from Testcomplete. Unfortunately Testcomplete can't get back the status code from the batch file to get the information if the script was executed successful or not. In many cases it would be useful to get back the status code at the keyword level of Testcomplete, for example: - execute a program to do some taks as pre condition for the following teststeps - execute some testcases with a batch file that can't be executed by Testcomplete directly, like python testcases with the pytest frameworkCommand Line and Collapsible Script Methods
Request 1: As of now, I have faced problems in passing variables from command line to TestComplete. So, if I would like to have a single suite, working for different regions/environments, and execute themfrom command line, I don't get an option to pass PARAMETERS to my Project or Project Suite. Consider having to work on 5 environments. When i evoke TC execution, I would like to pass arguments to my Project/Project Suite (can be said as Project or Project Suite Test Parameters). This will ease my work in simply passing my arguments for environments and other static data, which will accordingly execute my scripts with the correct configurations. Request 2: Another request, which I would want across all automation tools - Give a feature to collapse methods. It's quite tiring to go through the our scripts to find a method. I know, we can find it using the drop down, but it's not always that easy - It's hard to move up and down, with that much of code on the block. A similar approach like we have in Visual Studio - the ease of programming and maintenance just gets better.4.1KViews1like2Comments