Contributions
Working With An Oracle Database
We're currently having problems dealing with an Oracle database through TestComplete. It's very weird: we have the correct connection string and TestComplete can see the tables in the database, but there are some issues: 1. All the tables seem to be duplicated 2. When selecting a table in a database checkpoint, an error appears saying the table cannot be found. This happens in the query designer as well. We're using the "Oracle Provdier for OLEDB". We've also tried using the "Microsoft OLEDB Provider for Oracle" and while it didn't have problems connecting to the database, we are unable to select a table. These errors are very weird, I have attached a 2 minute long (wmv) video demonstrating the odd behaviors. Any light that can be shed on the problem would be very helpful. Thanks in advance.15KViews0likes3CommentsRe: Running the open project from a script
Thanks for the reply David. Because this test will be ran 3 times a night (each time with different server/database values for the variables), it's not logical for us to put the script as the first test item; if we do this the server/database variables will always contain the same values, unless we modify them manually. The way we've currently been doing it is making 3 copies of the project, each contains the different project variable values we need. This is very tedious however; when we want to make a change to the script we have to copy the project again 3 times and modify each one to contain the correct values for each variable. This is why it would be nice to be able to modify these variables first from the script and continue running the rest of the keyword tests. Better yet, it would be great if a user could modify these variables directly from the command line and run the test, something like: 10pm - "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run "\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs" /project:VisClient /var:Server=orion /var:Database=newdev /SilentMode 11pm - "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run "\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs" /project:VisClient /var:Server=aries /var:Database=testing /SilentMode ... and so on. I know this isn't currently possible, however it would be a great feature addition. For now, is there any way to modify the variables through a script and continue running the rest of the keyword tests?1.3KViews0likes0CommentsRe: Running the open project from a script
It's nice to see that after spending thousands of dollars on TestComplete it's hard to get decent support. They're antsy to make a sale but after the purchase the support goes downhill. The live chat agent [Matt] turns you to the email support (ignorantly), the email support takes days, doesn't look into your question but rather fires off the quickest answer they can think of [Tanya], which leaves the forum as the last resort. TestComplete is a great product, however AutomatedQA needs to throw a few more dollars into customer service and support.1.3KViews0likes0CommentsRunning the open project from a script
We currently have the need to use an automatic scheduler and run a TestComplete project from the command line using TestExecute. Before the project's keyword tests are ran, we need to change the values of a couple project variables. This is easy to do from the command line, we simply call a routine that exists in a script in the project. Our problem is, how can we continue running the project as soon as the variables have been changed? Here's the procedure that changes the values of the variables: procedure OrionNewDev; begin Project.Variables.Server := 'orion'; Project.Variables.Database := 'newdev'; end; We're calling the routine as follows: "C:\Program Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run "\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs" /project:VisClient /unit:Run /routine:OrionNewDev /SilentMode The support team has instructed us to use <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> <meta content="Word.Document" name="ProgId" /> <meta content="Microsoft Word 12" name="Generator" /> <meta content="Microsoft Word 12" name="Originator" /> &amp;amp;lt;BR /&amp;amp;gt; &amp;amp;lt;!--&amp;amp;lt;BR /&amp;amp;gt; /* Font Definitions */&amp;amp;lt;BR /&amp;amp;gt; @font-face&amp;amp;lt;BR /&amp;amp;gt; {font-family:"Cambria Math";&amp;amp;lt;BR /&amp;amp;gt; panose-1:2 4 5 3 5 4 6 3 2 4;&amp;amp;lt;BR /&amp;amp;gt; mso-font-charset:0;&amp;amp;lt;BR /&amp;amp;gt; mso-generic-font-family:roman;&amp;amp;lt;BR /&amp;amp;gt; mso-font-pitch:variable;&amp;amp;lt;BR /&amp;amp;gt; mso-font-signature:-1610611985 1107304683 0 0 159 0;}&amp;amp;lt;BR /&amp;amp;gt;@font-face&amp;amp;lt;BR /&amp;amp;gt; {font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; panose-1:2 15 5 2 2 2 4 3 2 4;&amp;amp;lt;BR /&amp;amp;gt; mso-font-charset:0;&amp;amp;lt;BR /&amp;amp;gt; mso-generic-font-family:swiss;&amp;amp;lt;BR /&amp;amp;gt; mso-font-pitch:variable;&amp;amp;lt;BR /&amp;amp;gt; mso-font-signature:-1610611985 1073750139 0 0 159 0;}&amp;amp;lt;BR /&amp;amp;gt; /* Style Definitions */&amp;amp;lt;BR /&amp;amp;gt; p.MsoNormal, li.MsoNormal, div.MsoNormal&amp;amp;lt;BR /&amp;amp;gt; {mso-style-unhide:no;&amp;amp;lt;BR /&amp;amp;gt; mso-style-qformat:yes;&amp;amp;lt;BR /&amp;amp;gt; mso-style-parent:"";&amp;amp;lt;BR /&amp;amp;gt; margin:0cm;&amp;amp;lt;BR /&amp;amp;gt; margin-bottom:.0001pt;&amp;amp;lt;BR /&amp;amp;gt; mso-pagination:widow-orphan;&amp;amp;lt;BR /&amp;amp;gt; font-size:11.0pt;&amp;amp;lt;BR /&amp;amp;gt; font-family:"Calibri","sans-serif";&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-font-family:"Times New Roman";&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-theme-font:minor-bidi;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-language:EN-US;}&amp;amp;lt;BR /&amp;amp;gt;.MsoChpDefault&amp;amp;lt;BR /&amp;amp;gt; {mso-style-type:export-only;&amp;amp;lt;BR /&amp;amp;gt; mso-default-props:yes;&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-ascii-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-font-family:Calibri;&amp;amp;lt;BR /&amp;amp;gt; mso-hansi-theme-font:minor-latin;&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-font-family:"Times New Roman";&amp;amp;lt;BR /&amp;amp;gt; mso-bidi-theme-font:minor-bidi;&amp;amp;lt;BR /&amp;amp;gt; mso-fareast-language:EN-US;}&amp;amp;lt;BR /&amp;amp;gt;@page Section1&amp;amp;lt;BR /&amp;amp;gt; {size:612.0pt 792.0pt;&amp;amp;lt;BR /&amp;amp;gt; margin:72.0pt 72.0pt 72.0pt 72.0pt;&amp;amp;lt;BR /&amp;amp;gt; mso-header-margin:36.0pt;&amp;amp;lt;BR /&amp;amp;gt; mso-footer-margin:36.0pt;&amp;amp;lt;BR /&amp;amp;gt; mso-paper-source:0;}&amp;amp;lt;BR /&amp;amp;gt;div.Section1&amp;amp;lt;BR /&amp;amp;gt; {page:Section1;}&amp;amp;lt;BR /&amp;amp;gt;--&amp;amp;gt;&amp;amp;lt;BR /&amp;amp;gt; KeywordTests.Test_Name.Run(); in the script after changing the variables, however this will only run one keyword test within the procedure. We need the entire project to run the way it's set up (see attachment), to the same effect as right clicking TestExecute's tray icon and selecting Run. Is this possible to do through scripting?16KViews0likes6Comments