Use Variables in the sql connectionstring
Hi there, I'm using 2 environments and 2 databases: 1 to create the testcases and 1 to execute them I want to check the results with DBTables Custom queries (SSMS) and I have i.e. next connectionstring: How CAN I make this string Variable ? When I login at the ALPHA-environment I want in the string ALPHA and server01 When I login at the BETA-environment I want in the string BETA and server02 Greetings, Sjef van Irsel
App does not work when manipulating mobile screen screen in TestComplete
I am currently setting up an appium server locally and using an actual device to create a test case for a native android app, but the app does not move when I operate (click, etc.) the app screen that is displayed on the mobile screen. (No response from buttons, etc.) Sometimes the app moves about 3 seconds after the click. The mirroring function of AndroidStudio worked fine on the same device and cable. If anyone knows of any solutions, please let me know.
desktop application using web elements
Hello, community! I am using TestComplete version 15.69.139 x64. At this stage, I am creating automated tests for a desktop application, but after the latest release, some elements of the application were replaced with web elements. Now, I am unable to create proper automated tests because TestComplete does not recognize these elements. I tried adding the -cdpAutoSetPort parameter to the command-line parameters, but this did not solve the issue either. Could you please advise on how this can be resolved? Thank you!TestComplete occasionally skipping a test step.
Hello all, I have made a test that has three steps, and am running it in an Azure DevOps pipeline. Step 1: Click 'Save and Close'. This is an ordinary button at the end of a form. Once it is clicked, the page takes some time to load the save (this varies between 3-20 seconds). During that time the page looks like this: Step 2: Click 'View Record'. This is a button that appears after the page has been loaded, and disappears about 5 seconds later. Note: Because of the variable time that it takes to save the record, I have set the Auto-wait Timeout for the step to be 30 seconds. This could then click on the object after the form was saved, no matter how long it took. Step 3: Click 'Save'. After the View Record button has been clicked, you are taken to the Record, and there is a Save button on the main page. Here are the three steps in the test: The test, when run in the pipeline, will occasionally fail with the following error: You would expect that the step right before the failure is Step 2: Click 'View Record'. But the picture shows that it is Step 1: Click 'Save and Close', and its place in the log also shows that it is Step 1. It jumps from Step 1 to Step 3: Click 'Save'. Of course, it can't find the Save button, because it hasn't clicked the View Record button (at least, there is no indication in the logs that it has). Does anyone have an idea of what is happening here? Thanks, littlebear
