I've searched but I can't find how to access things such as the Project Name, the Keyword Test name currently running and the currently running TestedApp. Others might be nice, such as the folder containing the Keyword Test.I'd like to access these from the Keyword Test and from scripts called from a Keyword Test.I'd also like access from a Script Extension at record-time.Another is variable substitution in the instructional text of a stored Manual CheckpointThe Project Name can be set once in the Project Variables. That's not too bad, but setting each Keyword Test name in each test's Variables is a bit much.Is there a pool of global variables or a method call somewhere, or some elegant tricks I need to learn?

I just pasted a line that had the code expression using KeywordTests.Test_Name.Variables.Variable_Name from one Keyword Test to another, and it magically changed the Test_Name to the test name of the 2nd test where I did the pasting. I don't see any such magic working in a script called from a Keyword Test, but it could be useful.

Can I ask what the need is for the access to the KeywordTest name and ProjectName? How are you using them in your automation project? Perhaps knowing the use case will help more in describing how to achieve what you're looking for.As for manual checkpoints, they are driven by the contents of a file as to what text displays. So, if you can update the file contents with new information on the fly (which can be done using various objects and tools of TestComplete) you can alter that displayed text on the fly.

I have to use some third-party programs to compare exported image files because they are too big for TestComplete to compare. TC quietly fails to do the compare and actually reports that the compare was successful. I reported this and was told the images are too big for memory. I have 4GB on this machine. The images are 1275x41220 pixels.The way I have it organized, the baseline files and my test-generated files to compare have paths and filenames containing the Project and Keyword Test names.The command-line programs that I use to split and compare the image files don't run on the WinXP 64bit machine where I use TC, so the Keyword Test pauses with a manual checkpoint instructing to copy/paste a command-line into a (32bit XP) VMware virtual machine. The VM can access the host directory where all the files are. Before comparing externally, I split the image into chunks small enough for TC to handle. I then click "Success" in the Manual Checkpoint when complete. Then the Keyword Test continues and runs a TC script that checks the directory for any chunks of the image that miscompare (the directory will be empty if they all compare OK). I run TC's compare method on the chunks that miscompare, which puts them nicely into the log file with the GUI tools to look at them. I obviously need to find replacement image tools that run on 64bit windows. I'm using a suite called Alchemy.So, one thing I'd like to do is modify the Manual Checkpoint text on the fly so that the command line that's pasted into the VM has the Project name and Keyword Test name as parameters for the DOS batch file. Even if I find 64bit replacement tools, my script still needs the Project and Keyword Test names to operate on the image files. I call this script from an if-then-else block that I copy/paste into each Keyword Test thast needs it. These lines contain the name of the Keyword Test (as the name of the Manual Checkpoint and the directory where the files are to be found). The Project name is already a variable in several places. This is where I'd code the Keyword Test name as a variable.I have (will have) hundreds of tests for a suite of 4 similar applications. I plan to clone the Project for each new version tested. I expect some number of Stores (Regions, mostly) to legitimately change from version to version, and I need to replace these stored Regions with the new image from the log (I wish there was a one-click way to do this, BTW) but still have the Stores intact for the older versions. That's why the Project name is part of the path for various baseline and temporary files. I currently set the Project name in the Project variables, which as I said is not too bad.

Rick, To get the project name, you can use the Project.FileName property, but it's ok to use a project variable for this too.As for keyword tests, to every test you need, you can add a variable, whose default value will specify the test name. You can do this on the Variables page of the Keyword Test editor. If you run your tests using test items, you can get the current test item name by using the Project.TestItems.Current.Name property.

Thanks, Alex. I missed finding both of those in the help doc.I tried the following directly in a Keyword Test, but it fails:Project.TestItems.Current.NameThe following code, copied from the doc into a script (and called from a Keyword Test) also fails!function Test(){ var TestItems; TestItems = Project.TestItems; Log.Message("The " + TestItems.Current.Name + " test item is currently running.");} The error message in both cases is "Object required".

Script access to variables for ProjectName, KeywordTestName, etc

17 Replies

AlexeyK
SmartBear Alumni (Retired)
13 years ago
Rick,

There was a similar feature request some time ago, so I increased its rating and described your case.

The request does not define a specific object, to which a method or property should be added. It just says that our users need a way to determine the current test name (test or script routine).

Sorry, I have no information to which object the new method or property will be added.

At the moment, I think, this will not be KeywordTests as this functionality can also be applied to script tests.
rickm
Contributor
13 years ago
That all sounds great. Thanks, Alex!
newbie23
Occasional Contributor
12 years ago
I like Rick's suggestion. But it would be nice if "Project.TestItems.Current.Name" could be smart enough to know if you are running as a project or individual keyword test for people like me that run one way for tests and another for debugging :)
newbie23
Occasional Contributor
12 years ago
Strike my last comment on having that path be able to tell whichever way it is running (as project, keyword, script)... I miss-understood how it was grabbing the name.

+1 on having the feature implemented so you can grab the name from keywordtests or from script - I would also use that quite a bit
rickm
Contributor
12 years ago
Yes, it took me awhile to finally understand that Project.TestItems refers to KeywordTests added to the Project's list of tests to run. The name that is returned from Project.TestItems.Current.Name can be different form the actual KeywordTest name since there is an editable field for this name.

I think I equated the name TestItems to KeywordTests because when you
click in the explorer panel to add a new KeywordTest, it says "add item".

What we want is something that might look like Project.KeywordTests.Current.Name, and it would always return the name of the KeywordTest no matter where it was run from. Something similar for scripts would be useful as well.

AlexeyK

SmartBear Alumni (Retired)

12 years ago

Rick,

What we want is something that might look like Project.KeywordTests.Current.Name, and it would always return the name of the KeywordTest no matter where it was run from. Something similar for scripts would be useful as well.

Rick, you can get the test name (test name, not test item's name) by using the following property:

Project.TestItems.Current.ElementToBeRun.Caption

Unfortunately, currently it works only for test items, not for script tests.

Scott,

Could you please describe what you need to know the current test name for? Developers are still gathering information for the feature... Your description would help us understand the problem. Also, maybe we'll be able to find another (better) solution.

matt_tarka
New Contributor
9 years ago
Why would I want to know the current keyword test name?

Because I archive files when running many keyword tests. When I archive the files, I want the archive location to contain the name of the test associated with the folder contents. Imagine yourself having 100 folders from different tests and asking yourself, which is associated with KeywordTestA, KeywordTestB, or KeywordTestC. In order to name, the folder I need the name of the keyword test, not TestItem.

Forum Discussion

Script access to variables for ProjectName, KeywordTestName, etc

17 Replies

Related Content

Variable declaration in a javascript class

Setting Excel filename as project variable

Test Complete / Variables

Duplicate server variables in OpenAPI

Issue sending Environment variable to TestComplete via Azure pipeline using command-line Parameters

Recent Discussions

Log.Error supressing Log.Warning in Execution Summary

TC15 Log Details shows # of tests with warnings/errors, not TC14's # of warnings/errors

Change the OS region format all at once

Keyword Test - Click - use -1, -1 by default?

Chrome/Edge Extension not always working... why?