Scribd Logo
Upload

Welcome to Scribd!

  • 18 views

    SQE Lecture 6

    Uploaded by

    sk knowledge
    This document discusses various aspects of software quality and testing. It defines software testing as analyzing a program to detect errors by comparing actual program conditions to required conditions. It outlines principles of testing such as having test cases define expected outputs and avoiding self-testing. It also describes different testing approaches like static testing, the software testing life cycle, and generic testing processes involving planning, design, execution, analysis and reporting. The goals, team, limits, and methods of software testing are also summarized.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    SQE Lecture 6

    Uploaded by

    sk knowledge
    18 views28 pages
    This document discusses various aspects of software quality and testing. It defines software testing as analyzing a program to detect errors by comparing actual program conditions to required conditions. It outlines principles of testing such as having test cases define expected outputs and avoiding self-testing. It also describes different testing approaches like static testing, the software testing life cycle, and generic testing processes involving planning, design, execution, analysis and reporting. The goals, team, limits, and methods of software testing are also summarized.

    Original Description:

    Good story book

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses various aspects of software quality and testing. It defines software testing as analyzing a program to detect errors by comparing actual program conditions to required conditions. It outlines principles of testing such as having test cases define expected outputs and avoiding self-testing. It also describes different testing approaches like static testing, the software testing life cycle, and generic testing processes involving planning, design, execution, analysis and reporting. The goals, team, limits, and methods of software testing are also summarized.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    18 views28 pages

    SQE Lecture 6

    Uploaded by

    sk knowledge
    This document discusses various aspects of software quality and testing. It defines software testing as analyzing a program to detect errors by comparing actual program conditions to required conditions. It outlines principles of testing such as having test cases define expected outputs and avoiding self-testing. It also describes different testing approaches like static testing, the software testing life cycle, and generic testing processes involving planning, design, execution, analysis and reporting. The goals, team, limits, and methods of software testing are also summarized.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 28

    Software Quality

    Engineering

    Muhammad Usman
    Software Testing
    “Testing is the process of executing a program or
    system with the intent of finding errors.” by
    Myers 1979
    Software testing is the process of analyzing a
    software item to detect the differences between
    existing and required conditions (that is, bugs)
    and to evaluate the features of the software item
    (IEEE, 1986; IEEE, 1990).
    PRINCIPLES OF TESTING
    Glenford Myers in his book “The Art of Software
    Testing” suggested the following testing
    principles.
    ◦ A necessary part of a test case is a definition of the
    expected output or result.
    ◦ A programmer should avoid attempting to test his or her
    own program.
    ◦ Thoroughly inspect the results of each test.
    ◦ Test cases must be written for input conditions that are
    invalid and unexpected, as well as for those that are
    valid and expected.
    STATIC TESTING APPROACH
    Examining a program to see if it does not do what it is
    supposed to do is only half the battle; the other half is
    seeing whether the program does what it is not supposed to
    do.
    Do not plan a testing effort under the assumption that no
    errors will be found.
    The probability of the existence of more errors in a section
    of a program is proportional to the number of errors already
    found in that section.
    Testing is an extremely creative and intellectually
    challenging task.
    Exhaustive testing is not possible but we can assure that all
    conditions have been exercised.
    TESTING LIFE CYCLE
    GENERIC TESTING PROCESS
     Test Planning:
    ◦ Define a software test plan by specifying a test schedule for a
    test process and its activities.
     Test Design and Specification:
    ◦ Conduct software design based well-defined test generation
    methods. Specify test cases to achieve a targeted test coverage.
     Test Set up:
    ◦ Testing tools (Environment Set-up)
     Test Operation and Execution:
    ◦ Run test cases manually or automatically
     Test Result Analysis and Reporting:
    ◦ Report software testing results and conduct test result analysis
    GENERIC TESTING PROCESS
     Problem Reporting:
    ◦ Report program errors using a systematic solution.
     Test Management and Measurement:
    ◦ Manage software testing activities, control testing schedule,
    measure testing complexity and cost.
     Test Automation:
    ◦ Define software test tools
    ◦ Adopt and use software test tools
    ◦ Write software test scripts and facility
     Test Configuration Management
    ◦ Manage and maintain different versions of software test suites,
    test environment and tools, and documents for various product
    versions.
    Software Testing Goals
    Requirements quality.
    ◦ SQA must ensure that the software team has properly reviewed the
    requirements model to achieve a high level of quality.
    Design quality.
    ◦ Every element of the design model should be assessed by the software team to
    ensure that it exhibits high quality and that the design itself conforms to
    requirements.
    Code quality.
    ◦ Source code and related work products (e.g., other descriptive information)
    must conform to local coding standards and exhibit characteristics that will
    facilitate maintainability.
    Resource Management
    ◦ A software team should apply available resources in a way that has the highest
    likelihood of achieving a high-quality result.
    ◦ SQA analyzes the allocation of resources for reviews and testing to assess
    whether they are being allocated in the most effective manner.
    SQA TEAM
    SOFTWARE TESTING LIMITS
     Due to the testing time limit, it is impossible to achieve
    total confidence.
     We can never be sure the specifications are 100% correct.
     Test engineers never be sure that they completely
    understand a software product.
     We never have enough resources to perform software
    testing.
     We can never be certain that we achieve 100% adequate
    software testing.
    TESTING METHODS

    Manual Testing
    Automated Testing
    MANUAL TESTING
    This type includes the testing of the Software
    manually i.e. without using any automated tool.
    In this type the tester takes over the role of an end
    user and test the software to identify any
    unexpected behavior or bug.
    Testers use test plan, test cases or test scenarios to
    test the software to ensure the completeness of
    testing.
    MANUAL TESTING
    Condition: Manual tests can be used in situations
    where the steps cannot be automated, e.g. to
    determine Usability Testing: This is an area in
    which you need to measure how user-friendly,
    efficient, or convenient the software or product is
    for the end users. Here, human observation is the
    most important factor, so a manual approach is
    preferable.
    In manual testing Tester will create test cases,
    execute test cases, and write bug report manually.
    Limitations: Load testing, performance testing.
    MANUAL TESTING

    • Manual testing allows for • More Time Consuming activity


    human observation, which may
    be more useful if the goal is • Boring and repetitive
    user friendliness or improved
    customer experience. • Efficiency depends on tester
    AUTOMATED TESTING
    Automation testing, also known as Test Automation, is
    when the tester writes scripts and uses another software
    to test the software.
    This process involves automation of a manual process.
    Automation Testing is used to re-run the test scenarios
    that were performed manually, quickly and repeatedly.
    Automation is a not a Replacement of Manual Testing.
    If done properly, automated software testing can help:
    ◦ to improve accuracy,
    ◦ speed up the testing process,
    ◦ increase test coverage, &
    ◦ ultimately provide greater confidence in the quality of the
    software being tested.
    AUTOMATED TESTING

    • Efficient (No variation in • Automated testing does not


    results). entail human observation and
    cannot guarantee user
    friendliness or positive
    customer experience.
    MANUAL VS AUTOMATED TESTING

    MANUAL TESTING AUTOMATED TESTING

    Time consuming and tedious Fast


    Huge investment in human Less investment in human resources
    resources

    Less reliable More reliable


    Non-programmable Programmable
    Manual Test is not reusable Automated Tests are reusable
    High risk on missing out something Less risk of missing out something
    STAGES OF TESTING
     Unit testing/Component Testing/Module testing
     Integration Testing
     System testing
     Acceptance testing • An over-seas review might take
    many days as each ―back and
    forth‖ can take a day, so it might
    take five days to complete a review
    instead of thirty minutes.
    • It is difficult for Project managers
    to track whether all changes have
    been reviewed
    TEST CASE
    A test case in software engineering is a set of
    conditions or variables under which a tester will
    determine whether an application or software system
    meets specifications.
    A test case has components that describes an input,
    action or event and an expected response, to
    determine if a feature of an application is working
    correctly.
    Result: Pass / Fail
    Test Suite: A collection of test cases.
    ◦ A test case may include many subsets.
    TEST CASE
    Test Case ID: It is unique number given to test case in
    order to be identified.
    Test description: The description of test case you are
    going to test.
    Revision history: Each test case has to have its revision
    history in order to know when and by whom it is
    created or modified.
    Function to be tested: The name of function to be
    tested.
    Test Setup: Anything you need to set up outside of your
    application for example printers, network and so on.
    TEST CASE
    Test Execution: It is detailed description of every
    step of execution.
    Expected Results: The description of what you
    expect the function to do.
    Actual Results: pass / failed
     If pass - What actually happen when you run the test.
     If failed - put in description of what you've observed.
    TRACEABILITY MATRIX
    Traceability Matrix is a document used for
    tracking the requirement, test cases and the
    defects.
    This document is made to convince the client that
    the coverage done is complete as end to end.
    This document contains Requirement ID, test case
    condition and bug ID.
    Using this document the person can track the
    requirement based on bug ID.
    TESTING TYPES
    Black Box Testing

    White Box Testing

    Gray Box Testing


    BLACK BOX TESTING
    Black box testing is also known as
    the functional testing.
    A software testing technique whereby the internal
    workings of the item being tested are not known
    by the tester. E.g., in a black box test on a
    software design the tester only knows the inputs
    and what the expected outcomes should be and not
    how the program arrives at those outputs.
    The tester does not ever examine the programming
    code and does not need any further knowledge of
    the program other than its specifications.
    BLACK BOX TESTING

    • Tester can be non-technical. • Chances of having repetition of


    • This testing is most likely to find tests that are already done by
    those bugs as the user would programmer.
    find. • It is difficult to identify all
    • Testing helps to identify the possible inputs in limited testing
    contradiction in functional time.
    specifications.
    • Test cases can be designed as
    soon as the functional
    specifications are complete.
    White-Box Testing
     White-box testing (also known as
    clear box testing, glass box testing,
    transparent box testing, and structural
    testing) is a method of testing software
    that tests internal structures or workings
    of an application, as opposed to its
    functionality (i.e. black-box testing).
     The meanings of “clear box” and “glass box” appropriately
    indicate that you have full visibility of the internal workings of
    the software product, specifically, the logic and the structure of
    the code.
     In white-box testing an internal perspective of the system, as
    well as programming skills, are required and used to design test
    cases. The tester chooses inputs to exercise paths through the
    code and determine the appropriate outputs.
    WHITE-BOX TESTING

    • As the knowledge of internal • As knowledge of code and


    coding structure is pre-requisite, internal structure is a
    it becomes very easy to find out prerequisite, a skilled tester is
    which type of input/data can needed to carry out this type of
    help in testing the application testings.
    effectively.
    • The other advantage of white
    box testing is that it helps in
    optimizing the code.
    GRAY BOX TESTING
    Gray box testing is a software testing technique that uses a
    combination of black box testing and white box testing. Gray
    box testing is not black box testing, because the tester does
    know some of the internal workings of the software under test.
    In gray box testing, the tester applies a limited number of test
    cases to the internal workings of the software under test. In the
    remaining part of the gray box testing, one takes a black box
    approach in applying inputs to the software under test and
    observing the outputs.
    This is particularly important when conducting integration
    testing between two modules of code written by two different
    developers, where only the interfaces are exposed for test.

    You might also like