Enabling Business Users for SAP Testing

George Wilson

SAP Implementation

SAP Testing Presents a Constant Challenge

Pressure for change

Technology Changes:Release upgradesEnhancement packagesService packagesInfrastructure adaptationsMigrations

Changes = Frequent Testing

Business Changes:Mergers & acquisitionsBPOProductsRegulatory

QA King-pin

SAP Testing Challenges

Quality Assurance is key Disparate teams

DepartmentalSkill gapsOff shoring

Access to informationProject statusReporting

Manual nature of testingAutomation is hard

Poll 1

Who does the testing?

1. Business users2. Business Analysts3. QA team4. Partner – on-site5. Partner - outsourced

Top Upgrade Challenges

Source 2010 SAP Upgrade Benchmark Survey – Panaya Inc

Effort Spent in Implementation

Winning Tactics in Testing

For SAP Testing Survival

Involve all Stakeholders

Poll 2

What are your plans with SAP? (Tick all that apply)

1. About to go through a technical upgrade2. About to go through a functional upgrade 3. Due to go live on new SAP implementation

Focus on testing

Plan and Manage Project Efficiently

Optimal project planning that empowers stakeholdersStay on targetSingle point of reference

Planning & Processes

Planning & Processes

Carry out Impact Analysis

Manual impact analysis takes time and is costlyPinpoint at specific problems at code level

Reduces riskReduces QA requirementsCut project timescales

Make Manual Testing Easier

AddressesUnit testingSystem testingRegression testingUAT

Performed byProfessional TestersSME’sBA’sEnd-users

Inadequately documentedOften the “Wild West”

Minimise Script Maintenance

Scripting code drivenHigh maintenance burdenLimited audienceTechnical specialists

Often shelf-wareSub Main

Dim Result(50) As IntegerDim i as IntegerDim NewResult as StringStartBrowser "http://pandora.ple.blahblah.co.uk/action.pega?f1000=SIGNON&profile=test3", "WindowTag=WEBBrowser"

Window SetContext, "WindowTag=WEBBrowser", ""Window WMaximize, "", ""

delayfor 3000Browser SetFrame,"Type=HTMLFrame;HTMLId=__pegMainFrame",""Browser NewPage,"HTMLTitle=PANDORA - TEST1",""

Result(1) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f5p1", "VP=Object Properties;Wait=2,30")Result(2) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f6p1", "VP=Object Properties2;Wait=2,30")Result(3) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f8p1", "VP=Object Properties3;Wait=2,30")Result(4) = EditBoxVP (CompareProperties, "Type=EditBox;Name=f9p1", "VP=Object Properties4;Wait=2,30")Result(5) = PushButtonVP (CompareProperties, "Type=PushButton;Name=@ACTION=|ENTR", "VP=Object Properties5;Wait=2,30")Result(6) = PushButtonVP (CompareProperties, "Type=PushButton;Name=@ACTION=|APPR", "VP=Object Properties6;Wait=2,30")Result(7) = PushButtonVP (CompareProperties, "Type=PushButton;Name=@ACTION=|BACK", "VP=Object Properties7;Wait=2,30")

For i = 1 to 3Select Case i

Case 1 InputKeys "robir"PushButton Click, "Type=PushButton;Name=@ACTION=|ENTR"

ProcessKnowledgeResultsData

Automation meaningless without re-use

Re-use is Key

Poll 3

Do you currently use a test automation solution to help you with your SAP QA process?

1. Yes – high degree of automation2. Yes – partially successful3. Used to – not maintained4. Mostly manual

Explore Test Automation

Application

Automation

High Risk

Manual

Why Test AutomationMay Fail

Extensive ramp-up timeLower on-going value

Skills Acquisition

Build Script Library

Automation partially available

Script Maintenance Cycles

Benefit ‘Black-outs’Shelf-ware Warning

Benefit

Effort

Time

Eff

ort

4-8+ months

Programmatic Test Tools

Falling Back to Manual Testing

Less challengingMore effort

Skills Acquisition

Build Script Library

Automation partially available

Script Maintenance Cycles

Benefit ‘Black-outs’Shelf-ware Warning Benefit

Effort

Time

Eff

ort

4-8+ months

Programmatic Test Tools

Fall Back to Manual Testing

Move Into Automation

Categorize manual test casesConvert to Automation

Automatically

Enhance withVariable dataValidation rulesData analysis

Maintain test casesDeal with constant changeSelf-healing

Daily Regression

Cross platformMulti actionBranchingError recovery

Manual

Auto

Table effectsUI – Db validationData Rules

Start: ManualTesting

Progress: AutomatedTesting

Test Cycles

Ensure End to End Testing

SOA NetWeaver PI, Tibco, Software AG, Web Methods, Websphere…

OracleSQLServerDB2

SAP PI Testing

Code-freeTestStubSimulateDrive

SAP Test Data

Raise order Despatch Invoicing GL processing

Incremental Roll-back

Automated Test Processes

SAP Testing Eco-System

Customer Example

Vertical:Drinks manufacturing & hospitality

Challenges:6 month cycle for testing of complex SAP upgradesBusiness users time limitations and limited technical skill

Original Solution:Manual and automated testing solution for use in all SAP updates and in building of regression packsSAP implementation & upgrades managed with Qualify

Customer Example

Vertical:Energy utility

Challenges:No testing teamBusiness users limited technical skill - no coding

Original Solution:Manual and automated testing solution for use in User Acceptance TestingSAP implementation & upgrades managed with Qualify

Success in SAP Testing

Current skills and resourcesAbility to adapt to changeRapid process

Not another bottleneck

Project visibility and controlGo-live decisions with confidence and minimal disruptionManage the entire quality process and test environmentKeep, extend, reuse

Questions?

www.origsoft.com

solutions@origsoft.com