Skip to Content

If you followed my Jumpstart your SAP Enterprise Support driven Test Strategy: Get into Position! blog you should now be familiar with the concepts of Custom Code Management and the fundamental aspects of building your Business Blueprint and operating the Reverse Business Process Documentation (RBPD).

Fig1.png

Fig 1. RBPD steps

My suggestion to you is to adopt the same structure that SAP will recommend as a best practice in both its online documentation and SAP Press 2nd edition of Testing SAP Solutions. Specifically, it is recommended structuring by Business Scenario, breaking these into their Business Processes and then into their Business Process Steps (more often transactions).

Fig2.png

Fig 2. Business Blueprint recommended structure

Once you have the foundations in place you will be able to leverage solution manager for a host of functions. In the context of test strategy you should now have your core business processes documented with process steps having at least:

  • A short text
  • SAP system via logical component
  • Transaction code

At this stage we could start talking about lean test systems, but rather than complicate things we’ll discuss that in a later article. You can now associate your test case with each process step.

Fig3.png

Fig 3. Sample test case in business blueprint from SAP Solution Manager

My rule of thumb is that if a business process is critical to operations (in some shape or form contributes to the operation of a revenue stream) it is imperative that it undergoes testing to protect the integrity of the business process within your change management process.

The next EGI’s to undertake to get an understanding of basic testing methodology using solution manager is Test Management I: SAP Test Workbench and Test Management II: Business Process Documentation.

                          

Now that the systems and manual test cases are in place you need to build on this and also document the following information:

What types of testing need to take place?

Who are the testers?

Where do the testers perform there testing?

When do you perform this scope of testing?

Your testing practice will be understood by the involved personnel upfront and there should be no confusion around who’s doing what, when. Almost always a project kick-off meeting should have a slide showing these details upfront.

To me, this is the core of test ‘strategy’, knowing your resources and knowing how to use them effectively.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply