Itanium / PI Upgrade

Itanium / PI 7.1

NNI Application Testing

Itanium / PI Upgrade Timings

Upgrade step Timing

September 5/6
September 28/29

October 15/16
November 5/6

November 14/15
January 17
Itanium upgrade testing

• Potential issues 99% connectivity related

• Test applications‘ „heart beat“

• No extensive application testing required!

PI Upgrade Testing

• Potential issues more related

to mapping rather than connectivity

• Thoroughly test critical business scenarios

• No need to test every single customer

unless flagged as potential risk or priority
PI Upgrade Testing – Roles & Responsibilities

• Application owner
– Appoints responsible testers
– Gives overall sign-off based on input from responsible testers

• Responsible Tester
– Provides Test data to HP Testing Team
– Evaluates Test results and gives sign-off

• HP Testing Team
– Execute Tests
– Fix any bugs directly related to the PI upgrade
PI Upgrade Testing – Preparation work

In this Meeting

• Agree on in scope / out of scope applications

• Agree on Solution Team SPOC per application

• Determine responsible testers

(adding this to XLS)

• Determine which interfaces require EBP involvement

(eg. change of IP-Adresses, AS2 certificates)
PI Upgrade Testing – Preparation work

Follow up asap

• Ensure responsible testers have appropriate level of access to

R- and A-boxes (for SAP PI and SAP-R/3)

• Feedback on charge for application testing service

 Norbert Anthony

• Mercury Training for responsible testers?

 Expectations to be clarified with Jeff / Charisse

• Communicate timings to EBPs where required

PI Upgrade Testing – Preparation work

By Wednesday 22-SEP-2009

• Have list of test cases per interface ready

• Have test data available for hand-over to HP Team

• Have test schedule agreed with EBPs where required