Migrate TestComplete Manual and Keyword Workflows
TestComplete migration starts by extracting the test intent that still matters. In webmate, that intent usually becomes manual validation in the Workbench, framework automation with Selenium, Appium, Playwright, or Cypress, or a combination of both.
Concept Mapping
| TestComplete term | webmate equivalent | Migration note |
|---|---|---|
| Deprecated manual tests | Manual test run in webmate | Keep the checklist intent, but store evidence as screenshots, findings, and comments. |
| Keyword test operations | Migration checklist plus reauthored automation | Extract the repeatable intent, then rebuild it in the framework that fits the target system. |
| Name Mapping / object repository habits | Locator strategy in Selenium, Appium, Playwright, or Cypress | Treat this as test-code design, not as a direct import task. |
| Test log artifacts | Test run artifacts and Workbench evidence | The evidence stays close to the migrated run. |
Practical Migration Order
- Export or inventory the manual and keyword assets you still rely on.
- Separate human-driven checks from repeatable browser or app flows.
- Recreate the human-driven flow as a named manual run in webmate.
- Reauthor the repeatable flow with the framework that fits the target system.
What to Keep Human-Driven
Keep these cases as manual or assisted Workbench flows first:
- visual inspection and exploratory checks,
- steps that depend on human judgement,
- accessibility or hardware behaviors you want to observe live,
- and unstable legacy flows that need to be understood before they are automated again.
What to Reauthor
Reauthor these cases as automation:
- deterministic browser flows,
- deterministic app flows,
- repeated smoke tests or regression checks,
- and anything that today depends on TestComplete remote browser or remote device execution.
When you need the underlying asset inventory first, continue with the helper scripts in Migrate TestComplete Automation Workflows .
Capturing Evidence During the Transition
During migration, the most useful pattern is often to run a manual verification in webmate before rewriting the automated part. That gives you current screenshots, findings, and comments you can compare against the reauthored tests.
Next Steps
- For manual execution, continue with Testing a Web Application or Testing a Mobile App .
- For automation reauthoring, continue with Migrate TestComplete Automation Workflows .