Several tips on how to simplify your first test.
The best way to learn how TestComplete works is to start using it. You can create a simple application and test it, but it’s much easier to make use of a sample application (Orders.exe) shipped with TestComplete.
However, if you use this application, you will have to close it each time you change data in its table, and before starting a test in TestComplete, you will have to open it again manually. If you forget to do this, your test won’t start. A special editor, TestedApps, was added to TestComplete to avoid this situation. Once you open your application, TestComplete saves the path to it. So, there is no need to open the application again before starting the test.
The image below shows the position of the TestedApps item in TestComplete’s window.
The whole testing process will become easier and faster if you use a special record button instead of creating test script manually. In this case, all you have to do after recording is to make necessary changes to the automatically generated script.
Also, unexpected windows may appear while you are testing this application. Unexpected windows cause errors during the test run. This may happen if you are working with some other programs or documents while testing. The issue is that the testing process is interrupted by unexpected windows. If such an error occurs, an error message is posted to the test log and TestComplete shows which window caused the error. On the image below, an unexpected window is marked with a red arrow.