reg : test cases

Former Member — Thu, 05 Apr 2007 13:40:26 GMT

hi friends can u pls. providing information abt writing test cases. i will b thankful if you could provide me some real time test cases. Thanks.

Re: reg : test cases

Former Member — Thu, 05 Apr 2007 13:53:47 GMT

Hi..Sekhar,

<b> what</b> TEST CASES U NEED??

be specific with your question as there are somany with different stmts or progs.

Ram

Re: reg : test cases

Former Member — Thu, 05 Apr 2007 14:06:22 GMT

Hi,

Let me know your email id. I shall send you few real time test cases.

Thanks,

Srinivas

Re: reg : test cases

Former Member — Thu, 12 Apr 2007 07:38:01 GMT

hi srinivas thanks for your response. here is my email id

boy.nextdoor2u@gmail.com

Re: reg : test cases

Former Member — Thu, 12 Apr 2007 07:49:15 GMT

Create a simple test case

Procedure

1. Record a BDC session of the transactions to be tested in the R/2 test system with the transaction SIRC.

2. Check that the BDC session is batch-input-compatible with the transaction SBDC.

You can use the following utility programs:

RSCATB00
Display screen definition

RSCATB10
CALL TRANSACTION with spooler data

RSCATB30
Display BDC session in SAP system format.

3. Call the CATT maintenance transaction in the SAP system and create a new test case.

4. Enter the type Remote R/2 test in the test case attribute screen. You are prompted for the R/2 remote system if you have not yet specified it. Specify the System.

5. Go to the function editor. Choose Edit ® Enter TCD.

6. Enter the file and session names in the Read R/2 BDC session dialog box. Choose Continue.
A new TCD entry is made in the function editor.

7. Parameterize the R/2 transaction input fields.

8. Save the test case.

Message check via SAPMSCEM 0001 also in R/2
The message check via screen SAPMSCEM 0001 is now also recommended for the R/2 System, particularly if the expected message numbers are between 001 and 010 because these numbers are also used for system errors with the message ID (work area) TT. In such cases a transaction with errors could pass as 'OK' if only the numbers and not the message ID are checked, so you should append the message screen SAPMSCEM 0001 to the screen list. Define the check for message number and work area in this message screen. This replaces Check Error which only checks the message number with a combined message number and work area check.

Create Transaction-Independent Test Case

Prerequisites

You must have an RFC link to the target system before creating a Remote R/2 test case.

Procedure

...

1. Call the CATT maintenance transaction in the SAP system and create a new test case.

2. Enter the type Remote R/2 test in the test case attribute screen. You are prompted for the R/2 remote system if you have not yet specified it. Specify the System.

3. Go to the function editor.

4. Refer to the simple test cases from which you want to assemble the transaction-independent test case, with the REF function.

5. Insert other CATT functions in the test case (e.g. table check).

6. Save the test case.

7. Manage the test case in the Test Organizer.

8. Run the test case and analyze the log.

if u need more test cases plz reply

or please follow the link below .you will get many test cases

http://help.sap.com/saphelp_nw04/helpdata/en/f4/3f9efc59a711d1bc84080009b4534c/frameset.htm

regards
ravish

plz reward if helpful

topic Re: reg : test cases in Application Development and Automation Discussions

reg : test cases

Re: reg : test cases

Re: reg : test cases

Re: reg : test cases

Re: reg : test cases