Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Testing Tools

Former Member
0 Likes
601

Which Testing Tools used in sap r/3 , explain each in brief.

4 REPLIES 4
Read only

Former Member
Read only

Former Member
0 Likes
558

Hi,

The testing tools we use are SE30 Runtime Analysis and ST05 SQL trace. which says that how much time taken for each select statement and how many times it hits the data base tables etc.

Thanks

Sarada

Read only

Former Member
0 Likes
558

Hi,

SAP TESTING

SAP users use CATT frequently to upload master data or to make changes to master data records. SAP Consultants and Abapers tend to use it for creating test data. The transactions run without user interaction. You can check system messages and test database changes. All tests are logged. The CATT records your keystrokes while performing the actual transaction. You then identify the fields that you wish to change in that view. Then export this data to a spreadsheet to populate with the data required. This is uploaded and executed saving you keying in the data manually.

For SAP R/3 we use CATT and ECATT tools.

Both are very useful tools and generally used for automated functional testing.Reduces a large amount of cost and human effort.

Even you can convert or call external tool scripts like mercury QTP etc from ECATT and run from ECATT itself.Also you can use these tools with solution manager to get awesome effortless testing and test plan management.

Check my weblogs.

Part-1:Shows how to create a Parameterize CATT script.

/people/community.user/blog/2007/02/05/create-and-migrate-catt-to-ecatt-part-1

Part-2:Shows how to migrate CATT to ECATT script.

/people/community.user/blog/2007/02/06/create-and-migrate-catt-to-ecatt-part-2

1./people/community.user/blog/2007/01/02/integrating-ecatt-mercury-qtp-part-1

This one shows the minimum configuration required for QTP and ECATT integration on client and server side.

2./people/community.user/blog/2007/01/15/integrating-ecatt-mercury-qtp-part-2

This one shows the standalone mode.e.g.mercury script is created and uploaded to ecatt and then executed from ecatt itself.Also,It is now possible to call this script from Solution manager.

3./people/community.user/blog/2007/01/22/integrating-ecatt-mercury-qtp-part-3

This one shows the integration mode which is most powerful as we can run QTP scripts from ECATT,Upload & download modify existing etc.

Thanks

Vikranth

Read only

Clemenss
Active Contributor
0 Likes
558

Hi sandeep,

you may cosider the use of unit tests, look at the details and links I gave in my answer

[unit and system tests|]

Regards

Clemens