Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 61 views

    SWTesting

    Uploaded by

    suveti_george
    The document discusses software testing. It defines software testing as "the process of analyzing software to detect differences between expected and actual conditions, known as bugs." It explains that software testing involves writing test cases, executing tests, logging results, and linking tests to requirements. The document also outlines different types of testing, like black-box versus white-box testing, and notes that the best approach combines different test methods based on a software module's criticality and risk level. Finally, it emphasizes the importance of testing, noting that bugs found early cost less to fix than those found later or in the field.

    Copyright:

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

    SWTesting

    Uploaded by

    suveti_george
    61 views9 pages
    The document discusses software testing. It defines software testing as "the process of analyzing software to detect differences between expected and actual conditions, known as bugs." It explains that software testing involves writing test cases, executing tests, logging results, and linking tests to requirements. The document also outlines different types of testing, like black-box versus white-box testing, and notes that the best approach combines different test methods based on a software module's criticality and risk level. Finally, it emphasizes the importance of testing, noting that bugs found early cost less to fix than those found later or in the field.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses software testing. It defines software testing as "the process of analyzing software to detect differences between expected and actual conditions, known as bugs." It explains that software testing involves writing test cases, executing tests, logging results, and linking tests to requirements. The document also outlines different types of testing, like black-box versus white-box testing, and notes that the best approach combines different test methods based on a software module's criticality and risk level. Finally, it emphasizes the importance of testing, noting that bugs found early cost less to fix than those found later or in the field.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    61 views9 pages

    SWTesting

    Uploaded by

    suveti_george
    The document discusses software testing. It defines software testing as "the process of analyzing software to detect differences between expected and actual conditions, known as bugs." It explains that software testing involves writing test cases, executing tests, logging results, and linking tests to requirements. The document also outlines different types of testing, like black-box versus white-box testing, and notes that the best approach combines different test methods based on a software module's criticality and risk level. Finally, it emphasizes the importance of testing, noting that bugs found early cost less to fix than those found later or in the field.

    Copyright:

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

    Software Testing

    Content

    1. What is SW Testing 2. Testing as a V-Cycle phase 3. Functional vs. Structural Testing 4. SW Testing importance 5. Practical exercises

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    What is SW Testing ? What it is not ?

    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 items" [IEEE 829 Definition].
    Software Testing is ... the process used to asses the quality of software a systematic activity (writing test specs, test execution, logging of results, linking to requirements) an activity done in parallel to development

    Software Testing is not a proof SW correctness debugging (Testing tries to find errors, Debugging is used to remove errors)

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    SW Testing in the V-cycle

    Software Testing is done in different stages of development process Build the right thing ? (validation)

    Build it right ? (verification)

    Build it right ? (verification)

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    SW Testing Paradigms
    Black-box test (system test) White-box test (module test)

    Function-oriented Based on the specification Proof of functional requirements

    Structure-oriented Based on the internal structure E.g. analysis of control-flow

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    SW Testing
    Black-box vs. white-box-testing - Conclusions
    Black-box-test Advantages
    Easier to use in comparison to white-box-test Access to the source code is not necessary

    Disadvantages
    Errors in the specification are not recognized using black-box-tests Additional functionalities not described in the specification cant be tested

    White-box-test Advantages
    Code coverage can mainly be calculated automatically

    Disadvantages
    Requirements which are not implemented are not found with this technique

    Which test approach is the best ?


    Combination of different test methods Selection of test methods and testing depth depends on the criticality and the risk of the SW Module

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    SW Testing Importance - bugs costs


    Low costs if errors are found in early phases of V-cycle Medium costs if errors are found in SW testing phase Huge costs when product is in the filed

    Toyota pedal recall in 2010: $2 billion loss !!!

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    Traceability
    SW Requirements Testcases

    Traceability Matrix
    9
    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    SW Testing Links

    Wikipedia: Software Testing Razorcat Tessy Vector TAE, application notes, etc

    10

    01/06/2011 Confidential.The Contents may only be passed on, used or made known with our express permission. All rights reserved.

    You might also like