cancel
Showing results for 
Search instead for 
Did you mean: 

pls send test cases for qtp mercury testing in sap - (or,del,billing)-urg

Former Member
0 Kudos

Test cases are reqd urgently for sales order,delivery ,billing,cust master data

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hai rakesh and nagendra

We are planning to test the integration of qtp testing with sap.The requirement is to know the efficacy (time) and cost effective aspect of qtp testing over sap testing

So i require some test cases in sd (sales order, delivery ,billing) so that i can perform the same in qtp testing

Hope the post is clear

Former Member
0 Kudos

hi

pls be clear whn posting a query..

====

Sap Testing Links

/people/sapna.modi/blog/2006/04/10/ecatt--an-introduction-part-i

/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation-150-tcd-mode-part-ii

/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation--sapgui-mode-part-iii

/people/sapna.modi/blog/2006/04/18/ecatt-logs-part-vi

http://help.sap.com/saphelp_47x200/helpdata/en/20/e81c3b84e65e7be10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/12/6efc3f8fc2c542e10000000a1550b0/content.htm

http://www.thespot4sap.com/Articles/SAP_Testing_Lessons_Learned.asp

http://www.sap-img.com/sap-catt.htm

Role of sap Consultant in Testing

http://www.sap-img.com/general/role-of-sap-consultant-in-testing.htm

http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm

http://infolab.stanford.edu/~burback/watersluice/node19.html

Unit testing deals with testing a unit as a whole. This would test the interaction of many functions but confine the test within one unit. The exact scope of a unit is left to interpretation. Supporting test code, sometimes called scaffolding, may be necessary to support an individual test. This type of testing is driven by the architecture and implementation teams. This focus is also called black-box testing because only the details of the interface are visible to the test. Limits that are global to a unit are tested here.

In the construction industry, scaffolding is a temporary, easy to assemble and disassemble, frame placed around a building to facilitate the construction of the building. The construction workers first build the scaffolding and then the building. Later the scaffolding is removed, exposing the completed building. Similarly, in software testing, one particular test may need some supporting software. This software establishes an environment around the test. Only when this environment is established can a correct evaluation of the test take place. The scaffolding software may establish state and values for data structures as well as providing dummy external functions for the test. Different scaffolding software may be needed from one test to another test. Scaffolding software rarely is considered part of the system.

Sometimes the scaffolding software becomes larger than the system software being tested. Usually the scaffolding software is not of the same quality as the system software and frequently is quite fragile. A small change in the test may lead to much larger changes in the scaffolding.

Internal and unit testing can be automated with the help of coverage tools. A coverage tool analyzes the source code and generates a test that will execute every alternative thread of execution. It is still up to the programmer to combine these test into meaningful cases to validate the result of each thread of execution. Typically, the coverage tool is used in a slightly different way. First the coverage tool is used to augment the source by placing informational prints after each line of code. Then the testing suite is executed generating an audit trail. This audit trail is analyzed and reports the percent of the total system code executed during the test suite. If the coverage is high and the untested source lines are of low impact to the system's overall quality, then no more additional tests are required.

http://www.acm.org/ubiquity/views/t_burns_1.html

Integration Testing

http://en.wikipedia.org/wiki/Integration_testing

http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243430,00.html

http://www.bitpipe.com/tlist/Integration-Testing.html

===

http://www50.sap.com/businessmaps/6D1236712F84462F941FDE131A66126C.htm

===

CATT stands 4 Computer Aided Testing Tool

Although CATT is meant for as a testing tools, many SAP users have now use CATT frequently to upload vendors master data and make changes to other master record.

SAP Consultant and Abapers tends to used it for creating test data.

With CATT, you don't have to create any ABAP upload programs and this save on development time. However, you still have to spend time on data mapping into the spreadsheet format.

The transactions run without user interaction. You can check system messages and test database changes. All tests are logged.

What CATT does is record you performing the actual transaction once.

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.

To perform CATT, it has to be enabled in your production environment (your systems administrator should be able to do this - SCC4).

You will also need access to your development system to create the CATT script.

________________________________________

<b>User Guide for Data Upload</b>

The use of CATT is for bulk uploading of data. Although CATT is primarily a testing tool, it can be used for the mass upload of data. The way CATT works is like a real user actually inputting on the SAP screen. You prepare a set of data that are required to be input into the system and execute what you called a Test Case and CATT will do the boring task of keying for you.

<b>Over-all procedure</b>

The over-all procedure to upload data using CATT is as follows:

• Creation of the CATT test case & recording the sample data input.

• Download of the source file template.

• Modification of the source file.

• Upload of the data from the source file.

<b>Details of each step are provided in the following paragraphs</b>.

Detailed Procedure

Creation of the CATT test case:

Creation of the test case is completed as follows:

• Execute Transaction SCAT

• Name the test case. Test case name must start with “Z”. It is also good practise to include the transaction code in

the test case name (e.g. Z_IE01_UPLOAD for the upload of equipment)

• Click the “Record” button.

• Enter the transaction code (e.g. IE01)

• Continue recording the transaction. Ensure data is entered into every field that is to be used during the upload.

• Save the test case.

<b>Download the source file template</b>

Download of source file template is conducted in two stages as follows:

• Creation of import parameters:

• Within transaction SCAT, Double Click on the TCD line in the “Maintain Functions” screen.

• Click the Field List button (Field list is displayed).

• For every field that you wish to upload data, double click in the Column New field contents (This creates an

import parameter).

• In the Maintain Import Parameter Pop-Up:

• Delete the default value if not required.

• Press Enter

• The New field contents column now contains the character & followed by the field name (e.g. &EQART). This

is the name of the import parameter.

• Repeat this for every field (in every screen) to be uploaded.

• Back out and save the CATT test case

• Download of source file template:

• Use the path GOTO -> Variants -> Export Default

• Select path and file name (e.g. C:\TEMP\Z_IE01_UPLOAD.TXT)

• Click Transfer

<b>Modify the source file</b>

The downloaded source file template is now populated with the data that is to be uploaded. This is completed as follows:

• Using Excel, open the tab-delimited text file.

• Do not change any of the entries that already exist.

1st row contains the field names.

2nd row contains the field descriptions.

3rd row displays the default values which are set in the test case.

4th row contains a warning that changing the default values in the spreadsheet has no effect on the actual default values.

• The data to be uploaded can be entered in the spreadsheet from row 4 onwards (delete the 4th row warning &

replace with data for upload).

• Save the file as a Text file (Tab delimited).

<b>Upload data from the source file</b>

Uploading the data is completed as follows:

• Execute the CATT test case

• In the Execute screen:

• Set processing mode to Errors or Background (your choice).

• Set variants to External from file.

• Click the Choose button and select the file to be uploaded.

• If uploading to another client, click the Remote execution button and select the RFC connection to the required client.

• If uploading to the current client, click the execute button.

====

Reward if USeful

Thanx & regrads.

Naren..

Former Member
0 Kudos

Hi Kishore,

Please elaborate on your requirement so that the other members of forum can help you.

If your requirement is generic in nature then a small search on SDN SD forum will help you to answer your query.

I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.

Moreover there is a separate section of FAQs with answers which will help you in great deal.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details

Regards,

Raklesh

Former Member
0 Kudos

please elaborate what exactly you want.

regards

pradeep