TEST PLAN

[Former Member]

Can anyone tell me wt is a test plan and how it is written in sap in any module like sd,fi?

Thank you

[Former Member]

Hi there,

Test plan is nothing but the detailed description of the test scenarios that you wanted to test as a SD consultant. It depends on the project scope & deliverables.

Testing is of the following types:

Unit testing: This is done as & when you finish the configs / developments in your related module. For eg inyour project if you have defined new sales structures, order types, item catg, you will test by loading a sales order in a sales area. You will check to see if you are able to log the sales order, check if the plant, item catg etc are proposed correctly. This is done only in 1 specific domain like SD, MM, PP etc by individual consultants. This is either done in test client in DEV server or in TEST server itself.

Integration testing: When all the consultants MM, FI, PP have completed all their configs / developments, you will together test the sales cycles to see if over all flow is working as per the requirement. For eg you will test that when a sales order is raised, materials planning is working fine, when PGI & billing is done if FI docs are getting updated correctly or if planned production orders are able to be raised successfully. Both Unit test & integration test are done before UAT.

User acceptance test UAT: This is the main test that is required to be done before moving the project into PROD. This is done by the business users not by the consultanst. The business users identify various test scenarios depending on the scope of the proj & deliverebles. Accordingly they will come up with various test scenarios to test the end - end flow. Number of test cases & num of scenarios depends on the complexity of the project. Each domain is tested with relation to other domains. Some times even the consultants also help the business users in identifying the proper test scenarios.

Regression test: This test is done to check if the existing processes are not effected by your new project. Codes / configs shouldnot effect the existing processes. To test that is the main intention here.

As a consultant you are expected to help the business in identifying the test scenarios, data setups, time lines etc. All this is called test plan. A test plan is the doc which will capture what scenarios are tested, who is the functional / business owner of the test cases, whos the contact point in the UAT, time lines of the UAT etc.

Regards,

Sivanand

[Former Member]

Hi H K,

There are usually 2 kinds of test plans:

1. Unit test: These scripts are used to test module specific transactions.

2. Integration test: Used to test integration scenarios.

As an example:

If I create a test script which contains input parameters and results for the Purchase to Pay Process, it is an integration test script. This will most probably start from an MRP test, the output of this test will enter the Purchase order step, which will then go into the GRN, which will then feed the IV which will then end with payment of the invoice generated in the previous step. The testing covers the end to end scenario and output of one step becomes the input for the next.

Whilst the unit test will just be Create Purchase order (ME21N) and will be a standalone test to show that the purchasing transaction works.

A unit test is thus a precursor to the integration test. The first one shows or checks that the individual transactions work and the second one, whether they work together.

Hope it helps!

Preethi.