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

What are the key best practices when recording a CBTA script?

  • Enter all data by keyboard (not history fill).
  • Avoid popups like date search.
  • Take output data from the GUI bottom message bar (or use a Checkpoint to grab it from the screen).
  • Use Checkpoints to validate (e.g. verify a tax rate = 6%).
  • Use Add Screenshot for audit screenshots.
  • Always exit the transaction and record the logout step (prevents stacked sessions during automated foreground execution).

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?
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?