Showing ideas with label Command Line.
Show all ideas
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)
... View more
See more ideas labeled with:
-
Command Line
-
Distributed Testing
-
Test Results
-
Web Testing
Write logging to the TestComplete/TestExecute/SessionCreator command line; mirroring the logging output by ReadyAPI TestRunner. Currently only the arguments are written to the command line, with no further updates until the test run has completed.
... View more
See more ideas labeled with:
-
Command Line
Status:
New Idea
Submitted on
08-15-2022
10:25 AM
Submitted by
HootyMcOwlFace
on
08-15-2022
10:25 AM
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 framework
... View more
See more ideas labeled with:
-
Command Line
-
Keyword Tests
-
Script Extensions
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)
... View more
See more ideas labeled with:
-
Command Line
-
Test Results
Status:
New Idea
Submitted on
05-01-2020
02:23 PM
Submitted by
garyschechter
on
05-01-2020
02:23 PM
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();
}
... View more
See more ideas labeled with:
-
Command Line
-
Data-Driven Testing
-
Desktop Testing
-
Keyword Tests
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.
... View more
See more ideas labeled with:
-
Command Line
as the title. maybe something like: /pi:NetworkSuite /t:MyNetworksuiteTest
... View more
See more ideas labeled with:
-
Command Line
-
Desktop Testing
-
Distributed Testing
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 them from 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.
... View more
See more ideas labeled with:
-
Command Line
Pls refer Case #00555209 for more information. We want to have ability to run the Testcomplete testcase using API and pass data to testcases externally on api call. Data is dynamic and should not be saved with the automated tests.
... View more
See more ideas labeled with:
-
Command Line
-
Desktop Testing
-
Script Extensions
Status:
New Idea
Submitted on
07-11-2023
08:24 PM
Submitted by
santoshayodhya
on
07-11-2023
08:24 PM
The current version of Chromium Embedded Browser supported by TestComplete is 88, but we need to develop automation for applications having version 102 and above, hence request to support the version 102 and above for achieving greater automation coverage using TestComplete.
... View more
See more ideas labeled with:
-
Command Line
-
Desktop Testing
-
Distributed Testing
-
Visualizer
as an example I made a few keywordtests that calculated certain dates. now in my project explorer there is no way to know where this test is being used. I try to use test parameters for a lot of things to reuse the tests in other places. that way i dont rewrite teststeps multiple times The same for Script functions. if i want to know where this function is being used it would be nice to see where this test/script is referenced.
... View more
See more ideas labeled with:
-
Command Line
-
Keyword Tests
-
Test Results
-
Web Testing
Hi, It would be very helpful to be able to parameterize the command line located in Tools--> Options --> Engines --> Stores. Currently we can pass as param only the file name. It would be nice if we could pass as param the entire command line or the folder a file resides as we need to have test scripts for various environments.
... View more
See more ideas labeled with:
-
Command Line
-
Desktop Testing
-
Web Testing