Software Testing Process & Trend

Embed Size (px)

DESCRIPTION

This is the slide deck that KMS's Director of Delivery presented at Can Tho University on Saturday, September 28th, 2013

Text of Software Testing Process & Trend

  • SOFTWARE TESTING METHODOLOGY & TREND

    September 2013 KMS Technology - http://kms-technology.com

    Vu Pham Delivery Director vupham@kms-technology.com

  • AGENDA

    Software Testing Process & Trends 20

    Automation Testing & Tools 20

    Future of Software Testing 20

    Q&A 30

    2

  • 2013 KMS Technology

    SOFTWARE TESTING PROCESS

  • AGENDA

    Testing Process Evolution

    Components of Testing Process Framework

    4

  • DEVELOPMENT PROCESS EVOLUTION

    60s: Waterfall 80s: RUP 00s: Agile 70s: V-Model

    5

  • DEVELOPMENT PROCESS EVOLUTION (CONT.)

    6

    Client Advantages Disadvantages

    Simple model and easy to manage Applicable for small software

    Big Design Up Front Defect detected at late phases High amounts of risk and uncertain

    Early testing involvement Clear relationship between test phases

    development phases

    Still possess limitation of sequential model Require high amount of documentation Duplication of testing effort

    Risk and uncertain are managed Testing activities and process are

    managed

    Heavy documentation Late customer involvement only at UAT

    Adaptable to changes Early client involvement - Avoid

    unrealistic requirements Avoid spending time on useless

    activities

    Require high-capable people Need representative from client Problem scaling up the architecture

  • SO HOW TESTING IS CHANGED?

    Black-box testing System testing Functional testing Part-time tester

    Grey-box testing System/Integration

    testing

    Functional testing Full-time tester

    White-box testing System-system Non-functional testing Fit-for-Use Professional tester

    7

    60 80: Nice To Have ~ 90: Should Have 00 : Must Have

  • AGENDA

    Testing Process Evolution

    Components of Testing Process Framework

    8

  • TESTING CENTER OF EXCELLENCE

    Test Solutions

    Automation Testing

    Performance Testing

    Mobile Testing

    Specialty Testing

    Best Practices

    Process Assessment

    Testing Estimation

    Continuous Process

    Improvement

    Exploratory/Risk-

    based Testing

    Quality

    Policy

    Guidelines &

    Templates

    Fundamental

    Testing Process

    Quality Metrics &

    Standards

    Plan Test

    Design Test

    Execute Test

    Close Test

    9

    TCoE = Processes + Practices + Solutions

  • WHY TEST SOLUTIONS?

    10

    About the Client Clearleap was the first company providing data streaming solution to offer a complete platform that allows TV everywhere possible

    Business Challenges

    Simulate high volume of concurrent

    users 100,000+ Complete within a tight schedule Limited budget for tool

    KMSs Solutions

    Tool Evaluation: Execute a proof of concept to evaluate both commercial and open source tools

    Planning: Determine a test strategy, approaches

    Test Design and Development: Design and develop scalable load testing architecture

    Execution and Reporting: Perform load testing and analyzing/reporting test results

    Achievements

    Developed a scalable solution based on Jmeter

    Extremely reduced the cost of testing and tremendously increased ROI

    Found critical performance issues

  • WHY TEST SOLUTIONS? (CONT.)

    It takes months to build up solution from beginning

    Cost of commercial tools v.s open source tools

    Effective solutions differentiates us from other vendors

    Typical Testing Solutions:

    Automation testing (web, desktop, mobile)

    Performance/Load Testing

    Security Testing

    Database/ETL Testing

    11

  • WHY BEST PRACTICES?

    12

    About the Client Global company supporting clinical trials in 67 countries. The Client offers services which include behavioral science, information technology, and clinical research

    Business Challenges 100% on time delivery with zero critical

    bugs Complicated paper process following

    FDA regulations Various testing platforms for both mobile

    devices and desktop

    KMSs Solution Process Establishment: Identify gaps in

    current process; Leverage start-of the-art practices

    Process Improvement: Define and measure performance /quality metrics

    Lifecycle Testing: Perform all lifecycle testing activities

    Test Automation: Develop an automation framework to shorten test cycle

    Achievements New process helps reducing 60% testing

    effort No critical defects identified during 1 year

    of engagement Moved paper work process to test

    management system open new trend in clinical trial industrial

  • WHY BEST PRACTICES? (CONT.)

    13

    Best practice improves outcome of activities

    Best practice has been proved of it effectiveness

    The more practices we use the higher maturity we are

    Typical Testing Best Practice:

    Review and Lesson-Learnt

    Root Cause Analysis

    Risk-based/Exploratory Testing

    Estimation Method, ROI Model

    Quality Metric Dashboard

  • Definition: CPI is an ongoing effort to improve quality of products, services, or processes

    In software testing CPI is seeking for improvement of: Quality

    Productivity

    Cost of Quality

    Time to Market

    CONTINUOUS PROCESS IMPROVEMENT

    14

    Assess

    Plan Implement

    Evaluate

  • Three metric categories in practice:

    Product Quality Metrics How good the overall quality of the product

    Process Effectiveness Metrics How the processes of delivery are performed

    Testing and Test Automation Metrics Detail status of testing activities, test outcome

    Metrics are standards of measurement by which efficiency, performance, progress, or quality of a plan, process, project or product can be assessed with the aim to support continuous improvement

    Wikipedia

    QUALITY METRICS

    15

  • Defects by Status Open Defects by Severity Open Defects by Severity & Functional Area Open Defects by Severity & Release Open Defect Aging

    Product Quality Metrics

    Defect Identification in Pre-Prod / Prod Weekly Defect Rates per Environment Defect Escape Ratio

    Defects by Phase Found / Functional Area Defects by Origin / Functional Area

    Process Effectiveness Metrics

    Test Coverage Planning Execution Status / Execution Rate by

    Functional Area/Cycle Defect Rejection Ratio Test Productivity

    Testing Metrics

    Percent Automatable Automation Progress Percent of Automated Testing Coverage

    Test Automation Metrics

    QUALITY METRICS (CONT.)

    16

  • Definition: Risk-based testing is testing method that base on identified risks to

    determine the right level of quality

    prioritize the tests and testing effort

    focus on most important testing areas first

    with the aim to be clear of current quality status and to get the best return by the time completing testing

    RISK-BASED TESTING

    17

  • EXPLORATORY TESTING

    18

    A style of testing in which you explore the software while

    simultaneously designing and executing tests, using feedbacks from the last test to inform the

    next. Elisabeth Hendrickson

    This type of testing helps: Discovering unknown and un-detected

    bugs

    Testers in learning new methods, test strategies, think out of the box

  • 2013 KMS Technology

    AUTOMATION TESTING & TOOLS

  • AGENDA

    Software Test Automation

    Software Performance Testing

    Tools Support Testing

    20

  • THINKING OF AUTOMATION

    Test Automation is

    Business values of Automation

    Greater Coverage More time for QA doing manual exploratory/risk-based

    testing.

    Improved Testing Productivity Test suites can be run earlier and nightly

    Reduced Testing Cycle Help shorten time-to-market

    Doing what manual testing cannot Load testing

    Using Testing Effectively Automation testing reduces tediousness,

    improve team morale

    Increased Reusability Tests can be ran across different platforms and

    environments

    The use of software and tools to perform the testing

    Code-Driven Testing at source code level with a variety of input arguments.

    GUI-Driven Testing at GUI level via keystrokes, mouse clicks, etc.

    21

  • THINKING OF RETURN ON INVESTMENT

    Tool, Implementation, Maintenance, Training,

    etc. Save Time, Early

    Response, Reliable, Repeatable, etc.

    ROI: The most important measurement for test automation ROI (effort): planning, development, maintenance, training, etc.

    ROI (cost): tool license, environment, management, automation resources, etc.

    ROI (quality): found defect, test coverage, etc.

    22

  • END-TO-END TEST AUTOMATION PROCESS

    1

    Assessment

    Evaluation

    2

    Pilot

    Planning

    3

    Design

    Implementation

    4

    Execution

    Report

    5 Maintenance

    23

    Plan Test

    Design Test

    Execute Test

    Close Test

  • ASSESSMENT & EVALUATION

    Assessment Understand organization vision,

    priorities, process & methodology

    Understand Application &a