Skip to Content
Personal Insights
Author's profile photo Nilabh .

Difference between using CBTA in testing over using Tricentis Tosca with SAP Solution Manager

Introduction:

CBTA (Component-Based Test Automation) and Tricentis Tosca with SAP Solution Manager are both tools used for software testing, but they differ in their approach and capabilities.

CBTA is a tool provided by SAP for test automation of SAP applications. It allows testers to record and playback test scripts for SAP applications, as well as reuse and customize test components. CBTA also provides features such as test data management, test result analysis, and integration with SAP Solution Manager.

Tricentis Tosca with SAP Solution Manager, on the other hand, is a more comprehensive testing solution that allows for end-to-end testing of SAP and non-SAP applications. It includes features such as model-based test automation, risk-based testing, and integrations with other tools for requirements management, defect tracking, and test data management.

One of the main differences between CBTA and Tricentis Tosca with SAP Solution Manager is the level of automation and ease of use. CBTA is designed to be a user-friendly tool for recording and playing back test scripts, while Tricentis Tosca with SAP Solution Manager is designed to be a more advanced tool for test automation and management.

Another difference is the scope of testing. CBTA is primarily focused on testing SAP applications, while Tricentis Tosca with SAP Solution Manager is designed for testing both SAP and non-SAP applications.

 

There are some additional differences between CBTA and Tricentis Tosca with SAP Solution Manager:

  1. Integration with SAP Solution Manager: Both CBTA and Tricentis Tosca integrate with SAP Solution Manager, but in different ways. CBTA is tightly integrated with SAP Solution Manager and leverages its capabilities for test planning, execution, and reporting. Tricentis Tosca, on the other hand, can integrate with SAP Solution Manager but also has its own test management capabilities.
  2. Scripting Language: CBTA uses SAP’s proprietary scripting language called ABAP (Advanced Business Application Programming) for test automation. Tricentis Tosca uses a model-based approach that abstracts away the underlying technology and allows for test automation using visual models.
  3. Test Data Management: CBTA has basic test data management capabilities, such as the ability to import/export test data and create test data containers. Tricentis Tosca has more advanced test data management capabilities, such as the ability to generate test data, manage test data variants, and mask sensitive data.
  4. Reporting and Analytics: Both CBTA and Tricentis Tosca provide reporting and analytics capabilities for test results. However, Tricentis Tosca has more advanced reporting features, such as risk-based analysis, traceability, and trend analysis.
  5. Non-SAP Application Testing: As mentioned earlier, Tricentis Tosca can test non-SAP applications, while CBTA is designed specifically for testing SAP applications. Tricentis Tosca has built-in support for testing various technologies such as web, mobile, API, and desktop applications.

Conclusion:

In summary, if you need a tool specifically for test automation of SAP applications, CBTA may be the better choice. However, if you need a more comprehensive testing solution that can handle testing of SAP and non-SAP applications,Tricentis Tosca with SAP Solution Manager would be a better fit.

CBTA and Tricentis Tosca with SAP Solution Manager have different strengths and capabilities, and the choice between them depends on your specific testing needs and requirements.

 

Keep learning and keep sharing. Cheers!

Assigned Tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Thomas Winkler
      Thomas Winkler

      Hi Nilabh .,

      not to forget to mention, that TTA needs an extra Windows Server Instance and CBTA is focused mainly on SAP Frontends.

      • Crucial for both is a stable and stringent SAP Process documentation (with defined SAP Process Scope's) ... in the right branch.
      • And don't forget the special defect handling (in project phase test is ITSM incident an defect) - this is an important improvement for all testing tools - because of the context information about the test cases and the reporting for it.

      BR Thomas

      Author's profile photo Michal Krawczyk
      Michal Krawczyk

      Hi Nilabh,

       

      With both CBTA and Tricentis Tosca you can also simulate 3rd party systems and EDI partners: https://open.sap.com/courses/iftt1-2-pc so as not to fall into this trap: https://blogs.sap.com/2023/04/02/e2e-testing-for-sap-is-a-mouse-trap-dont-fall-for-it-decouple-instead./

       

      BR,

      Michal Krawczyk