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

What three parts make up a CBTA test configuration?

Test configuration = test script + system data container + TDC.

  • Test script — the business-process steps of the automated case.
  • System data container — defines which systems the steps run on (by operational function SAP CRM/ERP, or by technical role dev/test/prod via logical component).
  • TDC (test data container) — a reusable data object with user-defined parameters, maintainable independently of the script.

Naming: CBTA configs use Z, composite configs use Y.

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 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?
How do you choose between CBTA versus a third-party automation tool?
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?