FastFactsFeature Presentation
February 22, 2010
We are using audio during this session, so please dial in to our conference line…
Phone number: 877-468-2134 Participant code: 182500
© 2010 The Johns Hopkins University. All rights reserved.
Today’s Topic• We’ll be taking a look at…
SAP User Acceptance Testing Kickoff
Today’s Presenters• Jayne Spence and Sam Press of Enterprise Business Solutions
(EBS)
Session Segments• Presentation
– Jayne and Sam will provide an overview of the upcoming SAP User Acceptance Testing.
– During their presentation, your phone will be muted.• Q&A
– After the presentation, we’ll hold a Q&A session. – We’ll open up the phone lines, and you’ll be able to ask
questions. – Jayne and Sam will answer as many of your questions as
time allows.
Contact Us• If you would like to submit a question during the presentation
or if you’re having technical difficulties, you can email us at: [email protected]
• You can also send us an instant message! – GoogleTalk – [email protected]– AOL Instant Messenger – HopkinsFastFacts– MSN – [email protected]
Survey• Survey
– At the end of this FastFacts session, we’ll ask you to complete a short survey.
– Your honest comments will help us to enhance and improve future FastFacts sessions.
User Acceptance Testing
Integration Testing for the SAP Upgrade
What is User Acceptance Testing?
• End users testing the system• Using a set of integrated scenarios with pre-
determined data• Final round of testing following EBS team testing • Ensure that the system operates as the user expects
Why do we do the User Acceptance Test?
• Uncover any issues not identified in previous testing cycles
• Allow end users to transact in the upgraded system and view any changes to it
• Provide user input to the business process owners to accept the system and sign-off for go-live
User Acceptance testing is not…
• A chance to change how the system or processes works
• A chance to recommend new functionality• The opportunity to create new test cases (except
after the execution of the prepared scripts, as time permits)
What is my responsibility as a tester?
• Follow the scripts as written• Analyze the results• Record results, include document number, PERNR or
other pertinent information for follow-on steps• Notify test support of failed steps
What do the scenarios look like?
• Scenarios are end-to-end strings of business processes that mirror daily work
• Each scenario was written by users familiar with the business processes and steps
• Spreadsheet format• Printed on paper for you to use for testing and
recording results
How is the test conducted?
• All testing is done in a room set aside for this purpose; Training Room 4 at Mt. Washington, Davis Building, second floor, 9 AM to 4 PM.
• We ask that users follow the schedule provided.• The laptops in the room have an icon to connect to
the QA (quality assurance) environment.
How is the test conducted? - continued
• Users have the same access as they have in production.
• The test support team will assist users with any issues.
• This team will open a JIRA (Issue Tracking software) for documenting any failed step.
• Users will turn in their marked up scenario sheets when testing is completed, or at the end of the day.
When is the testing?
• Testing begins on March 1 and continues through April 2.
• The core hours are 9 AM to 4 PM, Monday through Friday
• Specific assignments are available on the scheduling spreadsheet
• This is a five week period– First three are for scenario execution– Last two weeks for retest of failed steps
How is the test conducted? - continued
• If you use a Mac, we have two workstations for you to test from that platform.
• Other laptops have IE 7 or IE 8; all are marked.• BW runs overnight-all transactions finished by 7PM
will be available in BW for verification by 9AM the next day.
• Most tests will require only 1-2 days for execution.• You will be asked to return and retest failed steps
once remediation is complete.
What are the scenarios?
• Life cycle of a Grant• Life cycle of a Capital Project• Life cycle of Fixed Assets• Life cycle of Travel• Life cycle of AP• Procure to Pay• Finance Miscellaneous• HR/Payroll (completing on separate schedule)
Conclusion
• User Acceptance Testing is a way to be sure that the system works from the perspective of the business user.
• The results of this test are input to the go/no-go decision for taking the upgraded system live.
• EBS appreciates your time and effort in helping to make the upgrade of SAP a success.
• We’re going to open the phone lines now!• There will be a slight pause, and then a recorded voice will
provide instructions on how to ask questions over this conference call line.
• We’ll be answering questions in the order that we receive them.• We’ll also be answering the questions that were emailed to us
during the presentation.• If there’s a question that we can’t answer, we’ll do some
research after this session, and then email the answer to all participants.
Q&A
Thank You!• Thank you for participating!• We would love to hear from you.
– Are there certain topics that you would like us to cover in future FastFacts sessions?
– Would you like to be a FastFacts presenter?– Please email us at: [email protected]
Survey• Before we close, please take the time to complete a short
survey.• Your feedback will help us as we plan future FastFacts
sessions.• Click this link to access the survey…
http://connect.johnshopkins.edu/fastfactssurvey/
Thanks again!