Chris Hurst & Matt Huddleson, Comcast

Transcription

1 Chris Hurst & Matt Huddleson, Comcast Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

2 Session ID: BB2007 Speaker Chris Hurst - [email protected] Speaker Matt Huddleson - [email protected]

3 About Comcast Requirements Gathering and Test Planning Best Practices Effort Estimation & Test Environment Test Case Creation Test Monitoring Test Execution Test Result Reporting Dashboards and Metrics Defect Management Closeout Documentation Q&A

4 Provides entertainment, information, and communications products and services. The Cable Communications segment provides video, high-speed Internet, and voice services to residential and business customers. Serves 22.3 million video, 18.1 million high-speed Internet and 9.3 million voice customers In 2010 Comcast unveiled Xfinity as the new brand for their technology platform and products.

5 Gap Analysis POC for Questions Filter and Cross Reference Coverage Analysis Linked Defects Requirement Types Functional/Business Describe what a system should do Non-Functional/Performance Describe how a system should behave/perform

6 Key step in the planning of the life cycle. Estimation comprises effort evaluation of many activities in the PLC. Scripting and Execution are major portions of the estimate. Assumptions & Guidelines must be clearly stated. The best we can do is size up the chances, calculate the risks involved, estimate our ability to deal with them, and then make our plans with confidence. Henry Ford

7 Problem Environment unavailability blocks performance test execution Performance test results are not comparable with production Properly scaled physical environments are costly Virtualized Sizing Strategy Identify performance critical apps Understand the Environment Needs Identify common denominators Review with Tech Arch, App Dev, & Ops Solution Build the Cloud Optimal Virtualized Cloud Performance Environment Optimize Infrastructure meets phased demands Usage results in cost savings

8 Business Process Path Creation Status Requirements Traceability Reduce errors during handoff

9 VuGen for recording Multiple walkthroughs Align steps to test case Use defined names and naming convention

10 Knowing user experience isn t enough Visualize your test environment Convey complex topologies Identify dependencies and single points of failure View historical changes over time

11 Customizable views and graphs Monitor topology health

12 Out of the box analysis on performance response times, pass/fail ratios and SLAs SLA performance over time

13 Drill down on slow transactions and isolate long running components

14 View key end user, test profile and system utilization levels from a single graph

15 Customizable Workflow Cross Team Collaboration Traceability Field, Column and View Customization

16 Release Focus Public and Private Views Advance filtering One click copy to clipboard Simple URLs for sharing

17 The most common mistake of closeout reporting is simply restating what was already in the test execution report Focus on Major Events and Findings Executive Summary should stand by itself Be mindful of your audience (language and acronyms) Overview Clearly state what is in the Closeout/Summary Report Performance Test Results Summary Highlight positives and negatives Performance Recommendation (Go/No Go) Highlight changes from original plan/strategy Trending guidance Lessons Learned

18 Thanks for attending! We welcome your feedback. Primary Speaker Chris Hurst Co-Speaker Matt Huddleson