|
|
Document Categories:
- ABAPTM
- Adobe Forms
- ABAP-HR
- ALE & IDocs
- ALV
- BAPI
- BASIS
- BSP
- Business Workflow
- CRM NEW
- LSMW
- SAP Script/Smart Forms
- BI/BW
- eXchange Infrastructure (XI)
- Enterprise Portals (EP)
- eCATT
- Object Oriented Programming
- SAP Query
- Userexits/BADIs
- WebDynpro for Java/ABAPTM
- Others
What's New?
- Advanced Search Component for OneOrder Objects in SAP CRM 7.0 Part 2
- Advanced Search Component for OneOrder Objects in SAP CRM 7.0 Part 1
- HR-IC Enhancement Date TAB Addition
- Extend the standard SAP IMG Implementation Guide
- Installing MS SQL SERVER 2008 R2 DATABASE Software Manually
- Guide towards a simple conversion of an XML file to ABAP Internal table, using XML parsing
- Configuration of SAP HCM Structural Authorizations
- To print Transfer Order using smart forms instead of SAP script
- Handling Type 'E' messages from function modules
- Demo on bar code printing using SAP Scripts/Smart forms
- Advance usage of Print Workbench
- Creation and Usage of Freely Programmed Search Help In Web Dynpro for ABAP
- Material Master Enhancement End-to-End: Conversion Perspective
- Chem XML Message eStandards and CIDX Scenario Part III
- Using an Exit Plug in Web Dynpro for ABAP
- Step By Step Procedure to Enhance Standard BI/BW Extractor Using BADI
- How to maintain Query Translations in different languages
- Restricting Parked Document to Post using Business Transaction Events (BTE)
- Step-by-step guide to build object using Print Workbench
- Re-Processing inbound IDOC using WE02
- ABAP Quiz
Contribute?
Sample Specs
What's Hot?
eCATT (extended Computer Aided Test Tool)
eCATT Vs Mercury QTP
By Sapna
SAP eCATT is a automation tool meant for functional testing
in SAP. It comes with WAS. Latest version is WAS 6.40. It is made in ABAP.
QTP is Mercury's tool, which is a third party tool for automation testing. The
language used here is VB Script.
Both the tools are good. But the only drawback with eCATT as of now is that it
can execute web based SAP transactions except WebDynpro. So if the testing of
SRM, CRM etc is involved, one is forced to use QTP.
QTP takes the wrapping of eCATT and executes in SAP.
If only SAPGUI based transactions are involved in testing than eCATT is the best
tool to be used. And if web based transactions are also involved, forced to go
for QTP.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
Home • Contribute • About Us • Privacy • Terms Of Use • Disclaimer • Safe • Companies: Advertise on SAPTechnical.COM | Post Job • Contact Us
©2006-2007 SAPTechnical.COM. All rights reserved.
All
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software,
mySAP, ABAP, BAPI, xApps, SAP NetWeaver, and and any other SAP trademarks are
registered trademarks of SAP AG in Germany and in several other countries.
Every
effort is made to ensure content integrity. Use information on this site at your
own risk.
Graphic Design by Round the Bend Wizards
