DOCSLIB.ORG

Drive Continuous Delivery with Continuous Testing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Drive Continuous Delivery with Continuous Testing I Don’t Believe Your Company Is Agile! Alex Martins CTO Continuous Testing CA Technologies October 2017 1 Why Many Companies Think They’re Agile… They moved some Dev projects from waterfall to agile They’re having daily standups They have a scrum master Product owner is part of the team They are all talking and walking agile… And are talking about Continuous Delivery BUT… QA is STILL a Bottleneck… Even in DevOps Shops A 2017 survey of self- …of delays were occurring at proclaimed DevOps 63% the Test/QA stage of the practitioners found that … cycle. “Where are the main hold-ups in the software production process?” 63% 32% 30% 16% 22% 21% 23% http://www.computing.co.uk/digital_assets/634fe325-aa28-41d5-8676-855b06567fe2/CTG-DevOps-Review-2017.pdf 3 Challenges to Achieving Continuous Delivery & Testing IDEA Requirements 64% of total defect cost originate in the requirements analysis and design phase1. ? ? of developers time is spent 80% of teams experience delays in development and QA Development 50% 3 finding and fixing defects2 due to unavailable dependencies X X Security 70x required manual pen 30% of teams only security scan 50% more time spent on security test scan cost vs. automation10 once per year9 defects in lower-performing teams8 X X X 70% of all 63% of testers admit they 50% of time 79% of teams face prohibitive QA / Testing testing is still can’t test across all the different spent looking for restrictions, time limits or access manual4 devices and OS versions5 test data6 fees on needed 3rd party services3 ! Release 57% are dissatisfied with the time it takes to deploy new features7 ! ! Ave. cost of downtime per minute = $4,700 Operations Greater than 50% production outages from configuration management 53% percent of visits are abandoned if a mobile site takes more than three seconds to load What is Continuous Testing? First need to understand what it’s not! It’s not… Test Automation It’s not… Continuous Integration It’s not… Unit Testing It’s not… done only in the Test environment It’s not… a QA-led activity 5 What is Continuous Testing? The practice of testing across every activity in the SDLC to uncover and fix unexpected behaviors as soon as they are injected Most Customers Cannot Do Continuous Testing Today, But They Aspire To Get There…. 7 If This is Your Current SDLC You are waterfall X WEEKS X WEEKS X WEEKS Dev Test Agile Team: Design / Development / Unit Testing Integration & Central QA Release & Operations 8 If This is Your Current State You are water-SCRUM-fall X WEEKS X WEEKS X WEEKS X WEEKS X WEEKS Sprint 1 Sprint 2 Sprint 3 Agile Team: Design / Development / Unit Testing Integration & Central QA Release & Operations 9 If This is Your Current State You are not “really” agile X WEEKS X WEEKS X WEEKS X WEEKS X WEEKS X WEEKS User Sprint 1 Sprint 2 Sprint 3 Sprint N Stories Dev and Manual Sprint 1 Sprint 2 Sprint 3 Sprint N Testing Automated Regression Sprint 1 Sprint 2 Sprint 3 Sprint N Testing Release 10 What Testing at the Speed of Agile Should Look Like! In-Sprint everything to achieve “Continuous Testing” X WEEKS X WEEKS X WEEKS X WEEKS User Sprint 1 Sprint 2 Sprint 3 Sprint N Stories HIGHLIGHTS No Sprint-lag effect Dev and Exploratory Sprint 1 Sprint 2 Sprint 3 Sprint N Release in end of Sprint Manual Testing In-Sprint Test Automation Test Automated Scripting & Sprint 1 Sprint 2 Sprint 3 Sprint N Exectution Release Release Release Release 11 TESTING REALITY TESTING GOAL TOOLSET TEST TOOLSET TEST PYRAMID PYRAMID UI Tools UI 5% API Tools UI Tools 94% API 45% UI Dev Tools 50% API Tools API 3% Unit Dev Tools Unit 3% Non-functional: static, performance, security, etc… *Actual Customer Example of Their Testing Strategy Why are Traditional Testing Activities a Bottleneck? Testing hasn’t changed in the past 30 years Define an Idea or Write Manual Customer Needs Requirements Processes Enable Find/Create Automate Tests Identify Interfaces Identify Test Data Create Detailed Create Read Interfaces Test Data (usually Regression) (internal and 3P) Requirements Test Cases Requirements Requirements (real or virtual) Traceability Matrix Execute Create Defects Fix Defects Test Cases Achieving Speed Through Continuous Testing… Define an Idea or MODEL Customer Needs Requirements NOW ALL AUTOMATED Enable Find/Create Automate Tests Identify Interfaces Identify Test Data Create Detailed Create Read Interfaces Test Data (usually Regression) (internal and 3P) Requirements Test Cases Requirements Requirements (real or virtual) Traceability Matrix Execute Create Defects Fix Defects Test Cases A Different Perspective On An Old Challenge Too Many Unnecessary Manual Steps… Why not skip the intermediate steps? Create a diagram Convert it to text Interpret text Create app code, tests, data, scripts, etc. Intermediate activities are impediments to speed and quality 15 4 Pillars of Continuous Testing Code Correct? Automated Flow? Did developers create Can the application the application code Code Pipeline code flow across correctly? environments without Quality Automation manual intervention? Customer Application Are users perceiving value in the Experience Quality Did developers create application delivered? the correct features? User Value? Features Correct? THANK YOU 17.
Load more

Recommended publications
  • Core Elements of Continuous Testing
    WHITE PAPER CORE ELEMENTS OF CONTINUOUS TESTING Today’s modern development disciplines -- whether Agile, Continuous Integration (CI) or Continuous Delivery (CD) -- have completely transformed how teams develop and deliver applications. Companies that need to compete in today’s fast-paced digital economy must also transform how they test. Successful teams know the secret sauce to delivering high quality digital experiences fast is continuous testing. This paper will define continuous testing, explain what it is, why it’s important, and the core elements and tactical changes development and QA teams need to make in order to succeed at this emerging practice. TABLE OF CONTENTS 3 What is Continuous Testing? 6 Tactical Engineering Considerations 3 Why Continuous Testing? 7 Benefits of Continuous Testing 4 Core Elements of Continuous Testing WHAT IS CONTINUOUS TESTING? Continuous testing is the practice of executing automated tests throughout the software development cycle. It’s more than just automated testing; it’s applying the right level of automation at each stage in the development process. Unlike legacy testing methods that occur at the end of the development cycle, continuous testing occurs at multiple stages, including development, integration, pre-release, and in production. Continuous testing ensures that bugs are caught and fixed far earlier in the development process, improving overall quality while saving significant time and money. WHY CONTINUOUS TESTING? Continuous testing is a critical requirement for organizations that are shifting left towards CI or CD, both modern development practices that ensure faster time to market. When automated testing is coupled with a CI server, tests can instantly be kicked off with every build, and alerts with passing or failing test results can be delivered directly to the development team in real time.
    [Show full text]
  • Your Continuous Testing with Spirent's Automation Platforms
    STREAMLINE Your Continuous Testing With Spirent’s Automation Platforms DE RELE VE AS LO E P E T A ING T R G ES E T T S N U I O U IN T N E CO STAG Table of Contents Agile 3 What is Continuous Test (CT)? 4 What Hinders CT Implementation? 5 The Chasm 6 The Bridge 7 Spirent Velocity Framework 8 Lab as a Service (LaaS) 9 Test as a Service (TaaS) 10 CT Implementation Best Practices 11 Summary 12 2 of 12 Agile software development practices gained momentum in the late 90s. Agile emphasizes close collaboration between business stakeholders, the development team, and QA. This enabled faster software delivery, better quality and improved customer satisfaction. By employing DevOps practices, the pace and benefits are amplified. 3 of 12 What is Continuous Test (CT)? Continuous Test (CT) enables CT haed Cotuous terato ad Deery ee network testing to be more effectively performed by DEVELOP ITEATE STAGE ELEASE development teams by enabling them to take advantage of the QA team’s knowledge of real world customer use cases and environments. This is known as “shift left” because testing is moved earlier in the development cycle. With “shift left” tests are run as early as possible to accelerate understanding of AUTOMATE TESTS ORCHESTRATE TEST ENVIRONMENTSEXECUTE TESTS EARLIER problem areas in the code and where development attention is required. Why Do You Need CT? The combination of earlier and faster testing shortens time to release while improving quality and customer satisfaction. 4 of 12 What Hinders CT Implementation? Deficient or non existent Insufficient test Lack of test results Inadequate understanding of tools for creating resources for timely analysis tools hinder customer environments and automated tests test execution assessment of test results use cases by developers EW SOFTWAE DEVELOP ITEATE STAGE ELEASE SOFTWAE BILD ELEASE The promise of DevOps can’t be fully realized until Continuous Testing (CT) is factored in.
    [Show full text]
  • Continuous Testing Report 2019
    Continuous Testing Report In association with 2 Continuous Testing Report Contents Introduction 4 Executive summary 6 Current trends in continuous testing Test design 9 Functional and performance testing 13 Test data management 17 Test environment management 21 Test orchestration in the agile enterprise 24 Continuous testing: the road ahead 27 About the study 31 About the sponsors 37 3 Introduction Welcome dear readers. dependency on IT solutions today, with the integration of front-office and consumer-facing apps with back- Quality and testing approaches, methods, and office core systems, the leveraging of cloud and expertise have undergone radical changes over the microservices and the integration and use of IoT. And, last few years. Every organization today aspires on top of that, AI is emerging to make these solutions to deliver faster and more valuable IT solutions to autonomous and self learning. business and customers. To do this, they have been leveraging agile and DevOps methodologies and All this technology is delivered by different teams, using smarter automation technologies and as-a- many of which may not even be part of a single Service solutions to deliver IT faster and with greater company. flexibility. As we scramble to deliver innovative solutions for the At the same time, the IT landscape has also been newer, more complex IT landscape, there is, of course, growing in complexity. There is an increased a risk of failure. While some failures are inevitable and often provide a valuable learning opportunity (given a quick feedback loop), there are others that we must prevent from happening. Failures in core systems that seriously disrupt the business operations of an enterprise, failures that seriously impact a large number of clients and therefore jeopardize an organization’s reliability and brand perception, or failures in systems that cannot easily be rolled back all demand good testing of these systems before being deployed.
    [Show full text]
  • Continuous Quality and Testing to Accelerate Application Development
    Continuous Quality and Testing to Accelerate Application Development How to assess your current testing maturity level and practice continuous testing for DevOps Continuous Quality and Testing to Accelerate Application Development // 1 Table of Contents 03 Introduction 04 Why Is Continuous Quality and Testing Maturity Important to DevOps? 05 Continuous Testing Engineers Quality into DevOps 07 Best Practices for Well- Engineered Continuous Testing 08 Continuous Testing Maturity Levels Level 1: Chaos Level 2: Continuous Integration Level 3: Continuous Flow Level 4: Continuous Feedback Level 5: Continuous Improvement 12 Continuous Testing Maturity Assessment 13 How to Get Started with DevOps Testing? 14 Continuous Testing in the Cloud Choosing the right tools for Continuous Testing On-demand Development and Testing Environments with Infrastructure as Code The Right Tests at the Right Time 20 Get Started 20 Conclusion 21 About AWS Marketplace and DevOps Institute 21 Contributors Introduction A successful DevOps implementation reduces the bottlenecks related to testing. These bottlenecks include finding and setting up test environments, test configurations, and test results implementation. These issues are not industry specific. They can be experienced in manufacturing, service businesses, and governments alike. They can be reduced by having a thorough understanding and a disciplined, mature implementation of Continuous Testing and related recommended engineering practices. The best place to start addressing these challenges is having a good understanding of what Continuous Testing is. Marc Hornbeek, the author of Engineering DevOps, describes it as: “A quality assessment strategy in which most tests are automated and integrated as a core and essential part of DevOps. Continuous Testing is much more than simply ‘automating tests.’” In this whitepaper, we’ll address the best practices you can adopt for implementing Continuous Quality and Testing on the AWS Cloud environment in the context of the DevOps model.
    [Show full text]
  • Continuous Testing for Devops Evolving Beyond Simple Automation
    Technical Whitepaper 1 Continuous Testing for DevOps Evolving Beyond Simple Automation INTRODUCTION DevOps represents a cultural shift that stresses collaboration be- on acceleration. Moreover, adopting a bona fide Continuous Testing tween the business, developers, and IT professionals. Software test process (more than just automated tests running regularly) helps automation can enhance these connections and help organizations promote all of the core pillars of DevOps: Culture, Automation, Lean, achieve desired SDLC acceleration, but it’s important to recognize Metrics, and Sharing. that automation is just one piece of the DevOps puzzle. In this paper, we’ll explore why and how Continuous Testing’s real- Since testing is often one of the greatest constraints in the SDLC, time objective assessment of an application’s business risks is a optimizing quality processes to allow testing to begin earlier, as well critical component of DevOps. as shrink the amount of testing required, can have a marked impact DEVOPS PRINCIPLES There are several key pieces to understanding DevOps revolutions and they are often brought about by a compelling event at an organization, such as a shift to agile. As organizations start to move into an agile development methodology, they start to uncover other processes that can be accelerated, such as delivery by DevOps and testing by Continuous Testing. The acceleration that is set in motion via agile makes it necessary to accelerate the release schedule. In order to ensure a successful release, an organization must adopt continuous testing to make sure the conveyer belt does not break down. The modernization maturity model has these three distinct phases: AGILE Agile software development is a different way of thinking about approaching the challenge of development time.
    [Show full text]
  • Fuzzing Radio Resource Control Messages in 5G and LTE Systems
    DEGREE PROJECT IN COMPUTER SCIENCE AND ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2021 Fuzzing Radio Resource Control messages in 5G and LTE systems To test telecommunication systems with ASN.1 grammar rules based adaptive fuzzer SRINATH POTNURU KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Fuzzing Radio Resource Control messages in 5G and LTE systems To test telecommunication systems with ASN.1 grammar rules based adaptive fuzzer SRINATH POTNURU Master’s in Computer Science and Engineering with specialization in ICT Innovation, 120 credits Date: February 15, 2021 Host Supervisor: Prajwol Kumar Nakarmi KTH Supervisor: Ezzeldin Zaki Examiner: György Dán School of Electrical Engineering and Computer Science Host company: Ericsson AB Swedish title: Fuzzing Radio Resource Control-meddelanden i 5G- och LTE-system Fuzzing Radio Resource Control messages in 5G and LTE systems / Fuzzing Radio Resource Control-meddelanden i 5G- och LTE-system © 2021 Srinath Potnuru iii Abstract 5G telecommunication systems must be ultra-reliable to meet the needs of the next evolution in communication. The systems deployed must be thoroughly tested and must conform to their standards. Software and network protocols are commonly tested with techniques like fuzzing, penetration testing, code review, conformance testing. With fuzzing, testers can send crafted inputs to monitor the System Under Test (SUT) for a response. 3GPP, the standardiza- tion body for the telecom system, produces new versions of specifications as part of continuously evolving features and enhancements. This leads to many versions of specifications for a network protocol like Radio Resource Control (RRC), and testers need to constantly update the testing tools and the testing environment.
    [Show full text]
  • A Confused Tester in Agile World … Qa a Liability Or an Asset
    A CONFUSED TESTER IN AGILE WORLD … QA A LIABILITY OR AN ASSET THIS IS A WORK OF FACTS & FINDINGS BASED ON TRUE STORIES OF ONE & MANY TESTERS !! J Presented By Ashish Kumar, WHAT’S AHEAD • A STORY OF TESTING. • FROM THE MIND OF A CONFUSED TESTER. • FEW CASE STUDIES. • CHALLENGES IDENTIFIED. • SURVEY STUDIES. • GLOBAL RESPONSES. • SOLUTION APPROACH. • PRINCIPLES AND PRACTICES. • CONCLUSION & RECAP. • Q & A. A STORY OF TESTING IN AGILE… HAVE YOU HEARD ANY OF THESE ?? • YOU DON’T NEED A DEDICATED SOFTWARE TESTING TEAM ON YOUR AGILE TEAMS • IF WE HAVE BDD,ATDD,TDD,UI AUTOMATION , UNIT TEST >> WHAT IS THE NEED OF MANUAL TESTING ?? • WE WANT 100% AUTOMATION IN THIS PROJECT • TESTING IS BECOMING BOTTLENECK AND REASON OF SPRINT FAILURE • REPEATING REGRESSION IS A BIG TASK AND AN OVERHEAD • MICROSOFT HAS NO TESTERS NOT EVEN GOOGLE, FACEBOOK AND CISCO • 15K+ DEVELOPERS /4K+ PROJECTS UNDER ACTIVE • IN A “MOBILE-FIRST AND CLOUD-FIRST WORLD.” DEVELOPMENT/50% CODE CHANGES PER MONTH. • THE EFFORT, KNOWN AS AGILE SOFTWARE DEVELOPMENT, • 5500+ SUBMISSION PER DAY ON AVERAGE IS DESIGNED TO LOWER COSTS AND HONE OPERATIONS AS THE COMPANY FOCUSES ON BUILDING CLOUD AND • 20+ SUSTAINED CODE CHANGES/MIN WITH 60+PEAKS MOBILE SOFTWARE, SAY ANALYSTS • 75+ MILLION TEST CASES RUN PER DAY. • MR. NADELLA TOLD BLOOMBERG THAT IT MAKES MORE • DEVELOPERS OWN TESTING AND DEVELOPERS OWN SENSE TO HAVE DEVELOPERS TEST & FIX BUGS INSTEAD OF QUALITY. SEPARATE TEAM OF TESTERS TO BUILD CLOUD SOFTWARE. • GOOGLE HAVE PEOPLE WHO COULD CODE AND WANTED • SUCH AN APPROACH, A DEPARTURE FROM THE TO APPLY THAT SKILL TO THE DEVELOPMENT OF TOOLS, COMPANY’S TRADITIONAL PRACTICE OF DIVIDING INFRASTRUCTURE, AND TEST AUTOMATION.
    [Show full text]
  • Accelerate Software Innovation Through Continuous Quality
    Accelerate Software Innovation Through Continuous Quality 1 Software quality is recognized as the #1 issue IT executives are trying to mitigate. Enterprise organizations strive to accelerate the delivery of a compelling user experience to their customers in order to drive revenue. Software quality is recognized as the #1 issue IT executives are trying to mitigate. QA teams know they have issues and are actively looking for solutions to save time, increase quality, improve security, and more. The most notable difficulties are in identifying the right areas to test, the availability of flexible and reliable test environments and test data, and the realization of benefits from automation. You may be facing many challenges with delivering software to meet the high expectations for quality, cost, and schedule driven by the business. An effective software testing strategy can address these issues. If you’re looking to improve your software quality while achieving your business goals, Parasoft can help. With over 30 years of making testing easier for our customers, we have the innovation you need and the experience you trust. Our extensive continuous quality suite spans every testing need and enables you to reach new heights. 3 QUALITY-FIRST APPROACH You can’t test quality into an application at the end of the software development life cycle (SDLC). You need to ensure that your software development process and practices put a priority on quality- driven development and integrate a comprehensive testing strategy to verify that the application’s functionality meets the requirements. Shift testing left to the start of your development process to bring quality to the forefront.
    [Show full text]
  • An Experimental Evaluation of Continuous Testing During Development
    An Experimental Evaluation of Continuous Testing During Development David Saff Michael D. Ernst MIT Computer Science & Artificial Intelligence Lab The Stata Center, 32 Vassar Street Cambridge, MA 02139 USA fsaff,[email protected] ABSTRACT modern development environments that gives rapid feedback about Continuous testing uses excess cycles on a developer’s workstation compilation errors. This paper experimentally evaluates whether to continuously run regression tests in the background, providing the extra feedback from continuous testing assists developers in a rapid feedback about test failures as source code is edited. It is programming task without producing harmful side effects. intended to reduce the time and energy required to keep code well- It is good practice to use a regression test suite while perform- tested and prevent regression errors from persisting uncaught for ing development tasks such as enhancing or refactoring an existing long periods of time. This paper reports on a controlled human codebase. (Test-driven development [3] seeks to extend this situ- experiment to evaluate whether students using continuous testing ation to all development tasks: before each piece of functionality are more successful in completing programming assignments. We is added, a test for the functionality is written, added to the suite, also summarize users’ subjective impressions and discuss why the and observed to fail.) During development, running the test suite results may generalize. bolsters the developer’s confidence that they are making steady The experiment indicates that the tool has a statistically signif- progress, and catches regression errors early. The longer a regres- icant effect on success in completing a programming task, but no sion error persists without being caught, the larger its drain on pro- such effect on time worked.
    [Show full text]
  • API Testing Guide an Automated Approach to API Testing Transformation
    API Testing Guide An automated approach to API testing transformation. From Monolith to Microservice The consumerization of IT has changed the way we write applications today. Instead of building a single, monolithic system that is installed on a server in a back office or call center, modern When testing APIs, testers are faced with applications are scattered within mobile devices and web browsers numerous discrete units of work. Some so users can gain access to services at anytime from anywhere. of these APIs may have been created by a third party, while the possible And modern applications are no longer self-contained; they are ordering and combinations of different composed of multiple service components that are tied together versions of APIs can cause the number of at runtime. Therefore, the end-user experience is not powered by combinations that need to be tested to the elegant UIs we all use, but by APIs that facilitate interactions skyrocket to an impossible number. between code modules, applications and back-end IT systems. The ability to identify these combinations Because of this, the way we test must change. Quality assurance and then reduce them to a realistic (QA) and development teams must expand their capacity to test number without compromising quality each layer of the application, as well as the end-to-end business requires testers to adopt a transactions. Modern applications then require comprehensive API new model-based approach and invest in testing in addition to traditional UI testing. But API testing presents automation technologies. many challenges for testers. It requires a new approach—one that is automated wherever possible and inherently data-driven.
    [Show full text]
  • Parasoft Soatest the INDUSTRY-LEADING API TESTING SOLUTION
    Parasoft SOAtest THE INDUSTRY-LEADING API TESTING SOLUTION TRY IT Mitigate the risk of Reduce the cost of developing high-quality software, without sacrificing time-to-market: Get a free trial of Parasoft accelerated delivery with SOAtest and start testing. efficient end-to-end test CONTINUOUS TESTING automation. Automate the execution of API, performance, https://software.parasoft.com/soatest and security tests as part of your continuous Parasoft SOAtest helps cut through the delivery pipeline, leveraging CI infrastructure complexity of testing omni/multi-channel such as Jenkins, Bamboo, TeamCity, and API TESTING FOR applications. It extends API testing with VSTS, to provide a faster feedback loop ENTERPRISE AND automation and mitigates the cost of for test development and management. re-work by proactively adjusting your EMBEDDED library of tests as services change. AGILE Accelerate the feedback process required SOAtest efficiently transforms your in Agile methodology, by associating test existing test artifacts into security and • Automate complex scenarios cases with work items and integrating test performance tests, to increase re-usability across multiple endpoints (services, results with your requirements and issue and reduce redundancy, all while building databases, mobile, web UI, sensors, management systems, such as Jira, to a foundation of automated tests that ESBs, mainframes, etc.) from a single continuously validate your level of risk. intuitive user interface can be executed as part of Continuous Integration and DevOps
    [Show full text]
  • Automated Software Reliability Services Using Reliability Tools Should Be As Easy As Webmail
    Automated Software Reliability Services Using Reliability Tools Should Be As Easy As Webmail George Candea, Stefan Bucur, Vitaly Chipounov, Vova Kuznetsov, Cristian Zamfir School of Computer and Communication Sciences École Polytechnique Fédérale de Lausanne (EPFL), Switzerland Software quality assurance (QA) is boring, resource- ware, without human involvement from the service user’s hungry, labor-intensive, takes a long time, and is prone to or provider’s side.1 AutoSRS combines the concept of re- human omission and error. While research has offered a liability tools as a competitive, simple web service, with wealth of new techniques, few made satisfactory progress doing automated testing and debugging in the cloud, thus in all these directions, so industry still relies on relatively harnessing vast, elastic resources toward making such au- primitive techniques for software testing and debugging. tomation practical for real software. AutoSRS consists of: Little has changed in QA practice over the last 20 years. 1. Programmer’s sidekick that continuously and thor- Studies have found bug density in production-ready oughly tests code as it is written, with no upfront in- software to be staying constant over time, while average vestment from the developer; code volume of software is increasing exponentially, with 2. Debugging service that turns bug reports into 100% the net effect that the number of bugs per product is in- deterministically replayable bug scenarios; creasing. It is therefore necessary to quickly find a “dis- 3. Home edition on-demand testing service for con- ruptive technology” to reduce bug density by at least 10×. sumers to verify the software they are about to install We see two key challenges: First, few of today’s tools on their PC, phone, TiVo, camera, etc.
    [Show full text]