Breaking the Surface! Sara Allen Associate Director Of Analytics July 8 th, 2013 UAT Testing Process and Documentation for SAP Business Objects.

Slides:



Advertisements
Similar presentations
© Mark E. Damon - All Rights Reserved Another Presentation © All rights Reserved
Advertisements

$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500.
Because your patients come first. Coding Jeopardy OutpatientObservationInpatientER / CC 200 Final Jeopardy.
{Customer} Divisions Plan {Date} – {Version} Salesforce.com.
Science Jeopardy A B C D E
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
$100 $400 $300$200$400 $200$100$100$400 $200$200$500 $500$300 $200$500 $100$300$100$300 $500$300$400$400$500.
$100 $400 $300$200$400 $200$100$100$400 $200$200$500 $500$300 $200$500 $100$300$100$300 $500$300$400$400$500.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200.
Category 1 Category 2 Category 3 Category 4 Category.
Category Category Category Category Category.
Mr. Smith Cat. 1Cat. 2Cat. 3Cat
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
Calculating Quality Reporting Service
Theresa Valentine US Forest Service Corvallis Forest Science Lab
Instructions Play Game Quit Credit: U.S. Fish and Wildlife Service.
Performing Test Best Practices By Gabriel Rodriguez.
State of Connecticut Core-CT Project Query 8 hrs Updated 6/06/2006.
SERVICE MANAGER 9.2 VIEWS AND REPORTS July, 2011.
PointsParticipant Category A Category ECategory C Category.
Data Warehouse Overview (Financial Analysis) May 02, 2002.
Intro to HTML. HTML HTML = HyperText Markup Language Used to define the content of a webpage HTML is made up of tags and attributes Content.
May, 2010 Reporting Approach. Agenda  Background  Proposed Dashboards  Reporting Sub-Teams  Approach 2.
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
The Historical Investigation The York School
Category Heading Category Heading Category Heading.
Jeopardy Template By Carl Lyman © July 2007 Jeopardy Category 1Category 2Category 3Category
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
Bridges Policy Manuals for RSS Understanding and Navigating the SharePoint Manuals Updated: 10/22/2013.
Paramount Health Group Benefit Portal for XL India Employees
Slippery Slope
Blank Jeopardy. Category #1 Category #2 Category #3 Category #4 Category #
$100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300 $400 $500 $100 $200 $300.
WEBQUEST Let’s Begin TITLE AUTHOR:. Let’s continue Return Home Introduction Task Process Conclusion Evaluation Teacher Page Credits Introduction This.
Team 4Team 5 Team 6 Team 1Team 2Team 3 Round 2 Final Jeopardy Round 1.
Server-Side Scripting with JSP (2) ISYS 350. Post Back A postback is call to the same page that the form is on. In other words, the contents of the form.
Build It and They Will Come Designing Effective Writing Assignments Writing Across the Curriculum Workshop Center for Educational Practice.
Computers Are Your Future © 2008Prentice-Hall, Inc.
28/08/2015SJF L31 F21SF Software Engineering Foundations ASSUMPTIONS AND TESTING Monica Farrow EM G30 Material available on Vision.
Software Apps. Word, PowerPoint, Excel, Access Mr. Miller.
1 CALPADS UAT End of Year (EOY) Checkpoint Meeting May 9, 2012.
Database testing Prepared by Saurabh sinha. Database testing mainly focus on: Data integrity test Data integrity test Stored procedures test Stored procedures.
© Paradigm Publishing Inc. 9-1 Chapter 9 Database and Information Management.
Module 7: Data Entry (REDCap)
SAP ACROSS CAMPUS WE ARE ALL IN THIS TOGETHER Kathy Kraus North Idaho College July 30, 2015 Financial Aid-Colleague Coeur d’Alene, Idaho.
© Paradigm Publishing Inc. 9-1 Chapter 9 Database and Information Management.
Using SAS® Information Map Studio
1 CALPADS UAT End of Year (EOY) Checkpoint Meeting June 6, 2012.
ITGS Databases.
1 CALPADS UAT End of Year (EOY) Checkpoint Meeting May 2, 2012.
Component 8 Installation and Maintenance of Health IT Systems Unit 10 Developing a Test Strategy and Test Plan This material was developed by Duke University,
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Microsoft Office 2013 Try It! Chapter 4 Storing Data in Access.
SAP Employee Self Service Personal Data Overview Time Entry information not covered in this presentation.
Plan of Study: A Student’s Road Map to Success
Chapter 9 Database and Information Management.
UAT PROGRESS REPORT UAT: Project name Prepared by: Date: DD-MM-YYYY
APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)
APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)
LESSON 01 Hands-on Training Execution
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Project Name - Testing Iteration 1 UAT Kick-off
Module 7: Data Entry (REDCap)
9.2 User Acceptance Testing (UAT) Kick-Off
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Presentation transcript:

Breaking the Surface! Sara Allen Associate Director Of Analytics July 8 th, 2013 UAT Testing Process and Documentation for SAP Business Objects

UAT-User Acceptability Testing Process Overview Data Prep Data validation Joins BO Attributes Changes Critical Dates Report Validation Misc. Test

Overall Use of the Document: Tabs number correlate with the Test Case o Example: 400 correlate with Critical Dates Test Case Home Page: Date Tested and Sign offs- List the Names of all the testers Test Cases: o Test ID numbers for each item Example o List the Query criteria when applicable o List the expected results o PASS/FAIL o Retest Date o Comments- start with the date- then your comment-your initials. Example: 7/1/12- Smith was listed instead of Jones-SA

Data Prep – Regroup and really think through what we have. Circle back to the Data Inventory - do we have what we need? anything we don't? Naming Organization (in universe) Domain validation - do the attribute names describe the values in the data Data types, Format

Data validation (100) – This test case validates all of the data attributes and ensures that those data elements are displaying the correct values and the correct format, examples; mm/dd/yyyy, $, commas, text vs. numeric. Is everything there that we need?

Joins (200) - This test case validates how the data elements are joined with the tables at the source level. How are the attributes are joined/ fit together and what is the query criteria.

Counts and BO Created Attributes (300) - This test case validates that all the counts are counting accurately and that all attributes created only in BO function as defined in the requirements. Essentially testing the measures created by the Data Architect and validate the query criteria behind them.

Changes (400) - Tests the changes to the source system and how they are reflected in BO. Tests that all "track" data elements defined in the requirements, are actually tracking the history. This test case is testing how new data is introduced, which in essence is tracking the business process. We want to see how the data is populated, refreshed and tracked.

Critical Dates (500) - Testing that all critical dates and/or snapshots function as they should. Testing a point in time.

Report Validation (600) - Reconcile reports run from the core system against reports created and produced in BO. Misc. Test (700) - Any misc. test scenarios determined to test during UAT

Looking Ahead Whats Next? Universe will go into Production/Swan. Tidbits of advice to make testing less painful: Ask for help Patience is a virtue Communication is a must THANK YOU! PowerPoint presentation is saved on AMBR under data- warehouse>users-group.