Hi Sameer,
This is my First rep to this group as i have joined last night. And I thank Mr.Ramu for his light about SDN.
U must have understood what is UNIT TESTING as other folks given many replies,
<b>My views on integration testing according to <b>AcceleratedSAP</b>.</b>
In ASAP, a test plan that combines the defined resources, time frames, scope and procedures for performing integration testing.
It can be The testing a chain of business processes that flow together and cross functional boundaries.
Integration testing also involves outputs, interfaces, procedures, organizational design, and security profiles and focuses on likely business events and high-impact exceptions.
The Business Process Master List contains the following testing spreadsheets:
For "Integration test 1"(end-to-end scenarios), the testing scenarios focus on business cases that are within the R/3 environment, such as cross-functional or organizational boundaries, and R/3 authorizations.
For "Integration test 2", the testing scenarios also focus on the integration to external components, connecting many business cases to form a complete business cycle. The main focus is on testing R/3 with all interfaces, reports, all forms of output, EDI, ALE, and converted master data.
for practice u may test credit management scenario:
If you are using both the Accounts Receivable (FI-AR) component to manage your accounting and the Sales and Distribution (SD) component for sales processing, you can also use Credit Management to issue credit limits for your customers. You can make settings in Customizing to decide the scope of the check and at what stage in the process (for example, order entry, delivery or goods issue) a credit limit should take place. General information functions are also available for use with credit checks.
<b>Hope MY VIEWS will help you Out.
AZHAR S</b>
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.