SAP Solution Manager 7.2 · Component-Based Test Automation (CBTA)

How do you choose between CBTA versus a third-party automation tool?

Decide by the test-orchestration tool:

  • SolMan stores cases/execution/reports → use CBTA (Component-Based Test Automation, on the eCATT platform).
  • Orchestration is HP ALM → use UFT + SAP TAO.

Cross-system end-to-end tests (SAP + non-SAP) need a third-party tool like UFT for the non-SAP parts (data exchanged with TDCs via UFT). Other third-party options: HP UFT, Worksoft Certify.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Component-Based Test Automation (CBTA)

What three parts make up a CBTA test configuration?
What generation of test-automation tool is CBTA, and how does its modular approach cut maintenance?
What is a Test Data Container (TDC) in eCATT, and why is test data kept separate from the test script?
What are the key best practices when recording a CBTA script?
Why must SAP GUI scripting be TRUE before recording a CBTA script for a SAP GUI app?
What is a composite script in CBTA, and how does parameter exchange work in it?