Getting Started with TestComplete: Setup and Your First Test

Getting Started with TestComplete: Setup and Your First Test

TestComplete has a steeper setup curve than browser-native tools like Playwright. You're installing a full test IDE, configuring application connections, and working within a proprietary project format. This guide walks you through installation, project creation, recording your first test, and running it — without the trial-and-error most new users go through.

Prerequisites

Before installing:

  • Windows 10 or 11 (64-bit) — TestComplete runs only on Windows
  • 4GB RAM minimum, 8GB recommended — the IDE is memory-intensive
  • Admin rights — installation requires elevation
  • SmartBear account — free to create at smartbear.com, required for license activation
  • A valid license — trial licenses are available from SmartBear's website; they run 30 days

For web testing, you'll also need Chrome, Firefox, or Edge installed.

Installation

  1. Download the TestComplete installer from SmartBear's website after registering for a trial or purchasing a license.
  2. Run the installer. Accept the default installation path (C:\Program Files\SmartBear\TestComplete 15).
  3. During installation, select the modules you need:You can install all three and only pay for what your license covers.
    • Desktop — Win32, .NET, Java, Qt applications
    • Web — browser-based testing
    • Mobile — iOS and Android
  4. Install browser extensions when prompted. TestComplete installs Chrome and Firefox extensions automatically. For Edge, you may need to install the extension from the Edge Add-ons store separately.
  5. Launch TestComplete. On first launch, it will prompt for license activation.
  6. Activate using your SmartBear ID (the account you created above). For trial licenses, select "Activate online" and sign in.

Creating Your First Project

TestComplete organizes work into Projects and Project Suites. A Project Suite holds multiple Projects. For now, you need one project.

  1. Go to File → New → New Project Suite
  2. Enter a name (e.g., MyFirstTests) and choose a save location. Use a path without spaces — TestComplete handles some paths poorly with spaces.
  3. In the New Project wizard:
    • Project name: WebTests
    • Script language: Select JavaScript (most familiar for modern developers; Python is also a solid choice)
    • Test type: Select Web for this walkthrough
  4. Click Finish. TestComplete opens your new project.

The Project Explorer panel on the left shows your project tree:

  • WebTests (root)
    • KeywordTests
    • Script
    • Name Mapping
    • Stores

Configuring Your Browser

Before recording a test, tell TestComplete which browser to use.

  1. In the Project Explorer, right-click your project → Properties
  2. Go to Web Testing in the left sidebar
  3. Under Default browser, select Google Chrome
  4. Set the Page load timeout to 30 seconds
  5. Click Apply

Also verify the browser extension is active:

  • Open Chrome
  • Go to chrome://extensions
  • Find "TestComplete Web Extension" — it should be enabled

If it's not there, go to Tools → Install Browser Extension in TestComplete.

Recording Your First Test

Recording captures your mouse clicks and keyboard input, then generates a test script. It's the fastest way to get a working test, though recorded tests usually need cleanup.

Target application: We'll test a public demo site. Use https://the-internet.herokuapp.com/login (a well-known test site).

  1. In the Project Explorer, expand KeywordTests and double-click KeywordTest1 to open the editor
  2. Click the red Record button in the toolbar (or press Ctrl+R)
  3. The Record Test dialog opens. Select:
    • Browser: Google Chrome
    • URL: https://the-internet.herokuapp.com/login
  4. Click Start Recording. TestComplete opens Chrome and starts capturing.
  5. Perform the test steps:
    • In the username field, type: tomsmith
    • In the password field, type: SuperSecretPassword!
    • Click the Login button
    • Verify you see the "You logged into a secure area!" message
  6. Click the Stop Recording button (red square in the toolbar overlay)

TestComplete stops recording and populates your keyword test with the captured operations.

Understanding the Recorded Test

After recording, open KeywordTest1. You'll see a table of operations like:

Operation Object Value
Set Text page.txtUsername tomsmith
Set Text page.txtPassword SuperSecretPassword!
Click page.btnLogin
Wait page.flashMessage

Each row is a test step. Click any row to see its properties in the panel below.

Open Name Mapping in the Project Explorer. TestComplete automatically mapped the elements you interacted with. You'll see entries like:

  • Aliases.browser.pageLogin.txtUsername
  • Aliases.browser.pageLogin.txtPassword
  • Aliases.browser.pageLogin.btnLogin

These are the logical names your test uses to reference elements. If the page's element IDs change, you update Name Mapping once — the test doesn't need to change.

Adding a Verification Checkpoint

The recorded test doesn't verify anything yet — it just replays actions. Add a checkpoint to confirm the login succeeded.

  1. In the keyword test editor, click after the last row to position your cursor there
  2. Click Add Operation → Checkpoint → Property Checkpoint
  3. The checkpoint wizard opens. It needs you to point to an element on screen:
    • Click Point and Fix
    • TestComplete minimizes and waits for you to hover over an element in Chrome
    • Hover over the "You logged into a secure area!" flash message
    • Press Ctrl+Shift+A to capture it
  4. TestComplete brings you back to the checkpoint dialog. Set:
    • Property: innerText
    • Condition: Contains
    • Value: You logged into a secure area
  5. Click Finish

The checkpoint appears as the final step in your keyword test. If the element doesn't contain that text when the test runs, the test fails.

Running the Test

  1. In the Project Explorer, right-click KeywordTest1 → RunOr press F9 to run the entire project.
  2. TestComplete opens Chrome, navigates to the login page, and executes your test steps.
  3. When complete, the Test Log panel opens automatically.

Reading the Test Log

The log shows a tree of all executed steps. Each step has:

  • A green check (passed), red X (failed), or yellow warning
  • Timestamp
  • Screenshot (if captured)
  • Description

For a passing test, you'll see green checks for each step and a summary line: Test "KeywordTest1" Passed.

If the login fails (e.g., the site is down), you'll see a red X on the checkpoint step, with the actual vs. expected value, plus an automatic screenshot of the failure state.

Converting to Script

Keyword tests have limits. For anything beyond simple linear flows, working in script is more practical.

Right-click KeywordTest1 → Convert Keyword Test to Script. TestComplete generates JavaScript (or your selected language):

function KeywordTest1()
{
  var browser = Browsers.Item(btChrome);
  browser.Run("https://the-internet.herokuapp.com/login");

  var page = browser.Page("https://the-internet.herokuapp.com/login");
  page.FindElement("#username").SetText("tomsmith");
  page.FindElement("#password").SetText("SuperSecretPassword!");
  page.FindElement("button[type='submit']").Click();

  var flashMsg = page.FindElement(".flash.success");
  aqObject.CheckProperty(flashMsg, "innerText", cmpContains, "You logged into a secure area");
}

Open the generated script unit under Script in the Project Explorer. You can now edit the test directly in the code editor.

Running from Command Line

Once your tests are working in the IDE, you'll want to run them from a CI pipeline. The basic command:

TestComplete.exe "C:\Tests\MyFirstTests\MyFirstTests.pjs" /run /exit /exportlog:"C:\Results\log.xml"

Parameters:

  • /run — starts execution immediately on launch
  • /exit — closes TestComplete when execution finishes
  • /exportlog:"path" — exports the log to the specified file
  • /p:"ProjectName" — run a specific project (if the suite has multiple)
  • /test:"TestName" — run a specific test item

For CI, use /SilentMode to suppress dialogs that would block execution:

TestComplete.exe "C:\Tests\MyFirstTests.pjs" /run /exit /SilentMode /exportlog:"C:\Results\log.xml"

The exit code is 0 for pass, non-zero for failure — standard for CI integration.

Common First-Time Issues

"Application not found" error on launch: TestComplete can't find the executable it was configured to monitor. For web tests, ensure Chrome is the default browser and the extension is installed.

Elements not recognized after recording: The recorded properties may be too specific (e.g., dynamic IDs). Open Name Mapping, select the element, and change its identification criteria to use a stable property like id, name, or className instead of position.

Test plays too fast and fails: The application isn't ready before the next step. Add a Wait operation after navigation steps, or use Delay(1000) in script as a temporary fix while you identify the correct element to wait on.

Chrome extension blocked by policy: In enterprise environments, group policy may block browser extensions. Your IT team needs to whitelist the TestComplete extension ID.

License activation fails offline: TestComplete supports offline activation via a license file — contact SmartBear support to get an offline activation package.

Next Steps

Once your first test runs cleanly:

  1. Organize tests into Test Items — set up the execution tree in your project properties
  2. Add data-driven inputs — connect an Excel file to run the same test with multiple credentials
  3. Set up Name Mapping properly — review the auto-mapped elements and clean up any fragile identifications
  4. Integrate with CI — add the command-line execution to your Jenkins, Azure DevOps, or GitHub Actions pipeline

The getting-started hurdle with TestComplete is real, but once the project structure and Name Mapping are in place, the tests are genuinely maintainable at scale — which is why enterprises keep paying for the licenses.

Read more

Start now free