Forum Discussion
The ones I have converted were fine syntax-wise, but my Excel file turned out to be in a different place than TestComplete expected. Double-check the path definition in the Project variable and go look at the path it's using and make sure your file is actually there.
Hi Marsha,
I am new to TestComplete, so please bear with me. The only way I know to access the Project variables is via the tab at the bottom of the Workspace pane. Note: There are 2 other Tabs here as well, Test Steps and Parameters. When I view the Variables Tab, I only have one variable declared and that is my XLS file. The value is correct and does not look to have been changed. This Tab only appears when I select the Keyword Test in my Project Explorer.
When I select the Script Tab in the Workspace, the Test Steps, Variables and Parameters tabs go away. Where should I look for variables associated with the Script?
I am wondering if perhaps I set up my XLS data variable at the Keyword level instead of project level.
I await your great wisdom.
:-)
Bill
- Marsha_R10 years agoChampion Level 3
::looks around and fails to find Bag O' Wisdom::
Try double clicking on your project name in the Project Explorer and see if you get the tabs back on the bottom. Here's what mine looks like, and the DDT variables that were translated are all in the Temporary Variables list.
- BillA60310 years agoContributor
You are a genius !!!
Now I see the complete list.
I need to investigate further, but think I am headed in the right direction.
thanks
- BillA60310 years agoContributor
One thing that I am seeing is that it looks like each time I execute Convert to Script, a new temporary variable gets created.
For example, the XLS data file variable in my original Keyword test is named Ltctest1, type DB Table. I just ran Convert to Script and now a new temporary variable named Ltctest18 is in the list. The actual default value is the same as the original. This new variable is referenced inthe generated script code, however, not i all places. Some of my Log Message calls still reference Ltctest1.
Script:
Call Project.Variables.LtcTest18.Reset
While Not Project.Variables.LtcTest18.IsEOFyada yada yada......
I am guessing that I might be doing something wrong for this to be happening. Maybe my project is not right or my variable is declared in the wrong place or I have an incorrect setting.
Should I make my DB Table variable a persistent variable?
I appreciate any further guidance.
Related Content
Recent Discussions
- 2 days agoAndiiiA
- 3 days agomegha_phophalia
Log functions
Solved3 days agoAurore