Pre-Con Ed: Managing Test Data Across Distributed and Mainframe Systems

Editor's Notes

• #2: As you build out your presentation, here are a few dos and don’ts.
• #7: Who has a mobile banking app? How Critical is it? Technical issues, try again later – switch for a cash incentive instead? I think so! Tom experienced this recently while on the phone to a mortgage advisor! So we would consider testing this stuff a good idea? Yeah! - Tom’s ‘Family story’ Modern world apps provide HUGE business value and often considered critical, for example internet banking. Although the front end may be pretty and filled with benefits driven by APIs, what lies beneath can be complex and daunting – Developers and testers don’t know where to start, what to look for or how Legacy to Big Data platforms are related to one another.
• #9: This is your slide to set up the application economy… Dive into history of what has changed to drive companies to delivery software faster than they’ve ever had to before. End with discussion on this study from Oxford. Nearly 80% believe software-driven business models is the way to win. How much focus and effort will all your competitors, and even startups that you don’t know about, will use to drive the development of software to win your customers. What are you doing about it? What’s your strategy? (this leads into next slide… better deliver software like never before).
• #10: The application economy is characterized by escalating expectations from consumers, buyers, investors – living up to them can be quite a struggle 94% of executives face increased pressure to reduce time-to-market 30% of all businesses will monetize data assets by 2016 – those that don’t have the infrastructure in place to do so will be hungry for it. The middle stat is particularly interesting – two years ago, a quarter of all consumers stated they would abandon… +++ Just 12 months later, another survey reported that the number had shot up to 40% That is the pace of change in the application economy. So what our these CDOs and other LOB executives doing about it? *****
• #11: Research shows the aggregate IT spend for software testing is around $60 billion annually. Of that, $57.5 billion is spent on the labor, service, and environmental costs, while $2.5 billion is spent on the toolchain. So we need to significantly reduce the $57 billion dollar challenge by automating testing processes, and delivering with higher velocity and better quality.
• #13: Managing the development of applications has become a real balancing act. There is more pressure than ever to get new features out the door as quickly as possible, but then you’re also held accountable for quality. As development becomes more agile and gets better about reusing code, templates, they push more code to QA faster and it gets harder to keep up. Not to mention the need to test frequently and have the right data available at any time without having to wait. High Quality of Apps – 94% of business executives are facing increased pressure to release apps more quickly – Source DevOps Research commissioned by CA Vanson Bourne 2014 Over 60% of IT projects fail and 31.1% will be cancelled before completion - Source Standish Chaos Manifesto 2014 Only 16.2% are completed on-time and on-budget, While testing takes half the time in the SDLC 51% of online shoppers in the US say that site slowness is the top reason they’d abandon a purchase. – Source Testing can eat up to half of the budget – Source Bloor 2014 $312 billion a year is spent on software bugs - Cambridge University Judge Business School, 2013
• #14: The old adage about how do you eat an elephant – one piece at a time.
• #15: However, it’s really about DevTestOps. It’s an end-to-end practice for taking an idea, planning for it, building it, testing it to ensure quality, orchestrating its delivery into production and the ongoing operational practice that follows. Doing that successfully across the entire toolchain will eliminate points of friction across the software delivery lifecycle, enabling you to deliver code quickly and efficiently, while making sure it is aligned with the organization’s ability to support it. What we see is that Testing is really the ”final frontier” of DevOps.
• #21: In order to become an agile testing team, automation is key. With automated testing, especially of the APIs, teams can cover more tests and do it at lower cost. Not only are we talking about automated testing, but this also includes automating the release of code across the testing stages as well. And instead of wasting money and time of the setting up of physical environments for testing, these can be simulated to mimic production environments to run the right tests. In addition, the ability to take production data, mask it, subset it and meet privacy considerations, synthetic data generation will allow teams to build new data sets to cover new use cases, have data on demand, and better prepare themselves to meet compliance regulations. 100% test coverage from ASR cast study 640 Hours Forrester TEI SV study 95% based upon CA experience
• #25: Who has a mobile banking app? How Critical is it? Technical issues, try again later – switch for a cash incentive instead? I think so! Tom experienced this recently while on the phone to a mortgage advisor! So we would consider testing this stuff a good idea? Yeah! - Tom’s ‘Family story’ Modern world apps provide HUGE business value and often considered critical, for example internet banking. Although the front end may be pretty and filled with benefits driven by APIs, what lies beneath can be complex and daunting – Developers and testers don’t know where to start, what to look for or how Legacy to Big Data platforms are related to one another.
• #30: Nb.: include create data for OUTSOURCES
• #33: Increase security Eliminate Risk – By creating data that is production like but does not contain any real sensitive data, the risk of breaches due to test data leaving the org is reduced Increase Productivity – Clean up existing test cases, reduce testing cycles by 30% Provision data to dev teams within hours vs. days, create large volumes of data for performance and test loads, remove data dependencies and deliver data to multiple test teams at ones, testers no longer looking for data, making data, waiting for data, Increase Quality – cut defects by 95% Better Data = Better Results - Synthetic Data Benefits – can create more complex subsets, clone interesting bug scenarios, include outliers and ensure they are always available Test New Apps – create representative data when none exists Production data only coverts 10% to 20% of the needed data Agile – quickly and accurately reflect changes in the requirements and ensure data is up to date Visualization and diagraming enable agility Reduced Infrastructure Costs – Increased productivity quality and agility will save money Cost advantages over using production data - using the Test Data Warehouse, you eliminate the need to clone and maintain multiple databases for multiple testers which saves server, storage and related costs
• #35: Thank you for taking the time to meet with us today. With that, I’d like to….. (take questions, turn the time back over to, etc)