Support Pack Testing

Question

Hi all ,
            Can any one share or give their inputs on How the testing should be handled for BW support packs ? Basicaaly the test cases for both BW backend and BW frond end ?
Any input will be greatly appreciated.

Answer 1

I generally perform a triage process when looking thru the Notes.  If you haven;t already implemented Hot Fix and High Priority notes, I would review them first.  Then you make a pass through the other Notes:
- there may be components of BW that you don't use, e.g. SEM, MDX, or maybe notes for certain extractors you don't use.  Those Notes can pretty much be set aside - you shouln't have to do anything else with them.
- identify any notes that require you to do something as a prerequisite, e.g. perhapss there is an RSADMIN entry you need to make, or some other option that must be set somewhere. 
- identify any notes that require you to do something to take advantage of a new feature - this is different than the previous group of Notes that were required changes.  These would be broken up into two groups, Notes that sound like they deleiver somehting you really need/want right away, and those Notes that provide features that are less critical.
- identify the Notes that sound likethey make change that are important to your installation.  
-  there are Notes that fix really obscure problems that you have not encounted, and thos go into a low priority group.
- you'll probably have some Notes that require some reseacrh to gauge their impact.
I think once you have grouped the Notes, you should start to be able to get a feel for what needs a thorough test and review, and what might only warrant a quick check to make sure it still seems to work.
You'll need to perform basic config testing - can I create/change InfoProviders, InfoObjects, queries etc.
Test a representative sample of qureies, wkbks - BEx and web.
Test daily data load preocess which should include all the regular functions such as compression, rollup, change run, etc.
Test important BW Admin functions that you might not run every day, e.g PSA deletion, RSRV, etc.
Also review any more recent Notes that have been published for a future SP to make sure there is nothing in them that is of concern.