Scribd Logo
Upload

Welcome to Scribd!

  • 33 views

    Software Testing: Presentation ON

    Uploaded by

    Bhawna Madan
    This presentation provides an overview of software testing. It defines software testing as establishing confidence that a program does what it is supposed to do based on user requirements. The importance of testing is discussed as it evaluates quality, finds errors, and ensures customer satisfaction. Different software testing techniques are covered such as white-box testing, black-box testing, and testing at the unit, integration, and system levels. Common testing types and the software testing life cycle are also summarized.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd

    Software Testing: Presentation ON

    Uploaded by

    Bhawna Madan
    33 views23 pages
    This presentation provides an overview of software testing. It defines software testing as establishing confidence that a program does what it is supposed to do based on user requirements. The importance of testing is discussed as it evaluates quality, finds errors, and ensures customer satisfaction. Different software testing techniques are covered such as white-box testing, black-box testing, and testing at the unit, integration, and system levels. Common testing types and the software testing life cycle are also summarized.

    Original Title

    S1 final

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This presentation provides an overview of software testing. It defines software testing as establishing confidence that a program does what it is supposed to do based on user requirements. The importance of testing is discussed as it evaluates quality, finds errors, and ensures customer satisfaction. Different software testing techniques are covered such as white-box testing, black-box testing, and testing at the unit, integration, and system levels. Common testing types and the software testing life cycle are also summarized.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    33 views23 pages

    Software Testing: Presentation ON

    Uploaded by

    Bhawna Madan
    This presentation provides an overview of software testing. It defines software testing as establishing confidence that a program does what it is supposed to do based on user requirements. The importance of testing is discussed as it evaluates quality, finds errors, and ensures customer satisfaction. Different software testing techniques are covered such as white-box testing, black-box testing, and testing at the unit, integration, and system levels. Common testing types and the software testing life cycle are also summarized.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 23

    PRESENTATION

    ON

    SOFTWARE TESTING

    SUBMITTED BY:
    BHAWNA MADAN & DEEPA TOKAS
    B.Tech,VII sem, CS branch
    Laxmi Devi Instt. Of engineering & Tech.
    INTRODUCTION :
    DEFINITION:
    • Activity of establishing the necessary
    “confidence” that a program or system does
    what it is supposed to do , based on user
    specification
    • Finding errors
    • Identifying the differences between the actual
    and expected results
    • Major objectives of testing: Customer
    Satisfaction , Assuring Quality and Confirming to
    requirements
    IMPORTANCE OF TESTING
     Evaluates the quality and potency of the program for
    the required output
     Most important functionality in the SDLC as it exhibits
    all the mistakes and errors in the developed software
     An important parameter for the assured quality of the
    product
     In order to provide the customers an errorless S/W it is
    important for a company to go through the process of
    S/W testing
     Besides displaying the errors and rectifying them ,S/W
    testing also ensures the customer requirements
    throughout the product cycle
    SOFTWARE TESTING LIFE CYCLE
    (SUBSET OF SDLC)
    Initial requirements

    Create test plan

    Create test case

    Defect tracking

    Create bug report

    Retesting

    Summary report

    Close
    SOFTWARE TESTING
    TECHNIQUES
    WHITE-BOX TESTING
    • Sometime called structural testing or glass-
    box testing
    • Derivation of test cases according to
    program structure
    • Knowledge of the program is used to
    identify additional test cases
    • Objective is to exercise all program
    statements (not all path combinations)
    WHITE-BOX TESTING

    Test data

    Tests Derives

    Component Test
    code outputs
    BLACK-BOX TESTING
     An approach to testing where the program
    is considered as a ‘black-box’
     The program test cases are based on the
    system specification
     Test planning can begin early in the
    software process
    BLACK-BOX TESTING
    Inputs causing
    anomalous
    Input test data I behaviour
    e

    System

    Outputs which reveal


    the presence of
    Output test results Oe defects
    PAIRING DOWN TEST CASES
    • Use methods that take advantage of
    symmetries, data equivalencies, and
    independencies to reduce the number of
    necessary test cases.
    • Equivalence Testing
    • Boundary Value Analysis

    • Determine the ranges of working system


    • Develop equivalence classes of test cases
    • Examine the boundaries of these classes
    carefully
    TESTING LEVELS
     There are 3 levels:-
    UNIT

    INTEGRATION

    SYSTEM
    TYPES OF TESTING
     Sanity & Smoke  Configuration
     Compatibility
     Regression  Ad hoc
     GUI  Exploratory
     Functional
     Recovery
     Validation
     Security
     Performance
     Usability
     Retesting
     Scalability  Monkey
     Mutation  End to end
     Gorilla  Installation &
     Agile Uninstallation
    DOCUMENTATION
    There are 4 steps in documentation:-
     Test Plan
     Designing test case
     Executing the test case
     Defect reporting and management
    TEST PLAN:-
    (COMPLETE PLANNING BEFORE TESTING)
    FIELDS OF TEST PLAN:-
     Scope and objectives  Entry criteria
     Items to be tested:  Suspension criteria
    1. Features to be  Exit criteria
    tested.  Severity & priority
    2. Features not to be  Scheduling
    tested
     Testing type
     Roles &
    responsibility
    DESIGN TEST CASE
     A set of conditions or variables under which a
    tester will determine if the requirements are
    partially or fully satisfied.
     Often referred to as test script.
     Written test cases are often collected into
    test suites.
    EXECUTING TEST CASES
     After receiving build from development
    team, designed test cases are executed and
    actual values are entered in test case
    format.
     After comparing actual and expected value
    status for test case is entered as passed or
    failed.
    DEFECT REPORTING AND
    MANAGEMENT
     During test execution if a test case status is
    failed then tester detects a bug.
     He has to ensure this bug is not reported
    earlier and then he has to report it at senior
    level using defect report format.
    DEFECT REPORT FORMAT
    • Test case id • Assigned to
    • Project name • Reported by
    • Status • Test data
    • Severity • Expected result
    • Priority • Actual result
    • Test case summary • Result
    • Test case created • Description
    by • comment
    • Action to be taken
    BUG LIFE CYCLE
    AUTOMATION TESTING
     Testing using automation tools.
     Speed up testing process
     Can create test scripts and check all aspects
    of the application.
     Less investment in human resource.
     Overcome time constraints.
    QUICK TEST
    PROFESSIONAL(QTP)
     Originally written by MERCURY INTERACTIVE
    but was taken over by HEWLETT PACKARD.
     Automated testing software designed for
    testing various software applications and
    environments.
     Perform functional and regression testing
    using UI.
     Uses VBScript scripting language to specify
    test procedure
    CONCLUSION
    Testing is the process that never ends, it just
    get transferred from software engineer to
    the costumer. Every time the costumer uses
    the program, a test is being conducted. By
    applying the test case design, engineer can
    achieve more complete testing and thereby
    uncover and correct highest number of errors
    before ‘costumer test’ begins.
    QUERIES ????

    You might also like