TestProject End of Life: TestProject Alternatives and How to Migrate

What was TestProject?

TestProject was a free, community-based test automation platform for web, Android, and iOS apps. It launched in 2015 and was built on Selenium and Appium, both open-source testing tools, so teams got the reach of those frameworks without setting up drivers and grids themselves at the time.

Most teams used it in 3 ways:

• Recorders: a web and mobile recorder let testers build tests without writing code.
• An open SDK: developers wrote coded tests in Java, C#, or Python against TestProject's SDK and ran them through the same agents and reports.
• Agents, reports, and add-ons: a local agent ran tests on your own machines, results went to hosted reports, and the community shared add-ons that extended the built-in actions.

The price was the big draw. TestProject was free for everyone, which is why its shutdown left many small teams and solo testers looking for a replacement at the same time.

What happened to TestProject?

Tricentis acquired TestProject in 2019. It acquired Testim, a commercial AI-based testing tool, in February 2022. In November 2022, Tricentis announced that it would sunset TestProject and focus its resources on Testim, and it disabled new TestProject sign-ups on November 16, 2022.

TestProject reached end of life on March 31, 2023. Tricentis revoked all accounts and access on that date. Teams that had connected TestProject to qTest could no longer view, edit, or run their TestProject test cases and reports, although qTest kept its own test data.

So if you still have TestProject material today, it is whatever your team exported or kept in source control before the shutdown: SDK projects in Git, exported scripts, or notes on what the recorded tests covered. That is your starting point for any alternative.

What should you use instead of TestProject?

The right replacement depends on how your team used TestProject. Recorder users need a tool that records and plays back tests without code. SDK users need a tool that runs coded tests built on Selenium and Appium. Most teams need both, plus a way to run tests in CI.

Katalon Studio

Katalon Studio is the closest match to TestProject for most teams. Like TestProject, it is built on Selenium and Appium, it covers web, mobile, and API testing in one tool, and it lets testers record tests while developers write code in the same project.

Recording. Studio's Record Web (including Web Recorder Plus) and Record Mobile utilities capture your actions in the browser or on a device and turn them into test steps. You can play them back, edit them in a table view, and switch to code when you need more control.

Scripting. Script mode uses Groovy, which runs on the JVM, so Java code and Java libraries work in Studio projects. That matters for teams with TestProject SDK tests written in Java: the official TestProject migration guide shows how to bring them in.

Object repository. Studio stores locators once in a shared object repository and reuses them across tests, so a UI change is fixed in one place instead of in every test.

API testing. Studio tests REST, SOAP, and GraphQL APIs in the same project as your UI tests, and imports existing requests from Postman collections and OpenAPI (Swagger) specifications.

What you get depends on the plan, as listed on katalon.com/pricing as of November 2026:

• Studio Free plan: web, mobile, and API testing, basic record and playback for web and mobile, local execution, up to 40 static test suites, and Git-based source control. This is the direct replacement for a free tool.
• Studio Professional ($1,800 per seat per year, about $150 a month, billed annually): adds desktop testing, parallel execution, AI self-healing, dynamic test suites, the dual-mode debugger, behavior-driven testing with Cucumber, Jira and Azure DevOps integrations, and data-driven testing (a paid feature from Studio 11.7.0).
• Studio Enterprise (custom pricing): adds SSO, role-based access control, private cloud or on-premises deployment, and premium support.

Two add-ons cover the command-line, CI, and remote runs that TestProject's agents handled. Katalon Runtime Engine (KRE) runs Studio tests from the command line and in CI tools such as Jenkins, GitHub Actions, Azure DevOps, and GitLab, and it works with Professional and Enterprise. TestCloud runs tests on cloud browsers and devices. A 30-day free trial is available on the pricing page if you want to test the paid features first. If you already use Selenium directly, Katalon Studio vs Selenium explains what Studio adds on top.

Tricentis Testim

Testim is the tool Tricentis chose to focus on when it closed TestProject, so it is the natural option for teams that want to stay with Tricentis. It is an AI-assisted test authoring tool for web, Salesforce, and mobile apps.

As of November 2026, Testim offers a free Community plan, limited to one per organization, that includes web testing and unlimited local mobile runs on one parallel test, with support through docs and a community Slack channel. Testim says Community features are subject to change. Its paid plans (Testim Web, Mobile, and Salesforce) are quoted by sales. Testim is a different model from TestProject: tests are built in Testim's own editor, not on a Selenium or Appium SDK, so coded TestProject tests will not carry over.

Selenium IDE and Selenium WebDriver

If your team mostly used TestProject as a free recorder and code runner for web apps, the Selenium project itself is an option. Selenium WebDriver is open source, and its latest release as of November 2026 is 4.52.0 (October 29, 2026). Selenium IDE is its record and playback tool.

Be aware of the state of Selenium IDE. As of November 2026, the browser extension (version 3) is no longer maintained and is no longer in the Chrome Web Store, though it can still be installed for Firefox and Edge, and the new version 4 desktop app is released as beta builds. Selenium Manager now handles browser drivers automatically, and Selenium Grid is part of the project for parallel and remote runs, but you still choose and set up a test runner, reporting, and CI yourself. Our guide to Selenium IDE alternatives covers what it can and cannot do, and other recorders to consider.

Appium

For mobile tests, Appium is the open-source framework TestProject used under the hood, and it is still maintained by the OpenJS Foundation and its contributors, with Appium 3 as the current major version as of November 2026. Using it directly gives you full control and no license cost. Appium Inspector helps you find elements and has a basic recorder, but there is no full recorder like TestProject's and no hosted reports, so it suits teams with developers who are comfortable building their own framework.

How do TestProject alternatives compare?

This table compares the options that are live and maintained, as of November 2026. Katalon prices are from katalon.com/pricing, and competitor details are from each tool's own site.

How do you migrate from TestProject to Katalon Studio?

Whatever tool you choose, moving off TestProject is mostly a rebuild, not an import, because the platform and its stored tests are gone. The steps below assume Katalon Studio, but the first 3 apply to any tool.

A checklist for moving off TestProject

1. Inventory what you have. List the apps, flows, and test suites TestProject covered, and mark which tests were recorded and which were coded with the SDK.
2. Collect what survived. Pull SDK projects from Git, plus any exported scripts, test data files, and screenshots of old reports that show expected results.
3. Prioritize. Rebuild the tests that guard releases first, such as login, checkout, and core API calls, and leave rarely run tests for later.
4. Set up Studio. Install the latest Katalon Studio (11.7.0 as of November 2026), create a project, and connect it to Git.
5. Rebuild recorded tests with the recorders, and move coded SDK tests with the docs guide (both below).
6. Organize and stabilize. Move locators into the object repository, group tests into test suites, and run them locally until they pass consistently.
7. Set up CI. Add Katalon Runtime Engine (KRE) on a Professional or Enterprise plan to run suites in your pipeline, and TestCloud if you need cloud browsers and devices.

Moving coded SDK tests

If your team wrote TestProject tests in Java with the SDK, the Katalon docs guide shows how to run them in Studio. You need a TestProject project, the TestNG-JUnit Keywords plugin from the Katalon Store, and a basic understanding of JUnit and TestNG. Katalon's sample repository on GitHub, Katalon-Migration-TestProject, shows a finished example.

The docs guide covers Java SDK projects. Tests written with the Python or C# SDK need to be rewritten, either in Studio (Groovy or Java) or as plain Selenium or Appium tests in the same language.

Step 1. Get your TestProject-based project, or download the sample project.

Step 2. Import the required JAR files from your project's Gradle build file in the project settings. See dependency management with Gradle.

Step 3. Add your project files under Include > scripts > groovy.

Step 4. Fix compatibility issues. As of November 2026, the docs say Katalon Studio does not support JUnit 5, so change the JUnit 5 lifecycle annotations to their JUnit 4 or TestNG equivalents: @BeforeAll becomes @BeforeClass, and @AfterAll becomes @AfterClass. Then add a @Test annotation before the void execute() method.

Step 5. Initialize the Katalon driver inside the @BeforeClass method. For a web application:

WebUiBuiltInKeywords.openBrowser("");

WebUiBuiltInKeywords.maximizeWindow();

driver = DriverFactory.getWebDriver();

For a mobile application:

String dirName = RunConfiguration.getProjectDir();

MobileBuiltInKeywords.startApplication(dirName+"/App/APIDemos.apk", false);

driver = MobileDriverFactory.getDriver();

Step 6. Add the class name to your TestNG XML file.

Step 7. Update the test cases to use TestNG or JUnit keywords, then run the test.

Step 8. Check the results in the execution log.

Moving recorded tests

Recorded TestProject tests cannot be imported, so rebuild them with Studio's recorders. Open Record Web, enter the URL of your app, choose a browser, and repeat the flow the old test covered. For mobile apps, use Record Mobile with a connected device or emulator. Record Mobile uses a local Appium installation, which Studio's docs walk you through. Studio saves the captured elements to the object repository, so later tests reuse them.

Once recorded, review each test: add verification steps where the old test checked a value, replace hard-coded data with variables, and give tests clear names that match your inventory from the checklist.

Running your tests in CI

TestProject's agents ran tests on schedules and from CI. In Katalon Studio, Free covers local runs. To run suites from the command line, in Docker, or in Jenkins, GitHub Actions, Azure DevOps, or GitLab, you need Katalon Runtime Engine (KRE), an add-on for Professional and Enterprise plans. Studio can generate the command for a test suite, which you paste into your pipeline.

Which TestProject alternative should you choose?

Choose Katalon Studio if your team used both TestProject's recorders and its SDK, tests web and mobile apps, and wants one tool that records and runs code on Selenium and Appium. Start on the Free plan, and move to Professional when you need parallel runs, desktop testing, or self-healing, and add the KRE add-on to run tests in CI.

Choose Testim if you want to stay with Tricentis, mainly test web, Salesforce, or mobile apps, and are fine rebuilding tests in its editor.

Choose Selenium or Appium directly if you have developers who want full control, mostly wrote coded tests, and are willing to build the runner, reporting, and CI around them.

For most former TestProject users, the quickest path is to rebuild the highest-value tests first and run them locally before scaling up. You can start with Katalon Studio on the Free plan and compare plans on the pricing page.