Scribd Logo
Upload

Welcome to Scribd!

  • Tute 2

    Uploaded by

    Pubudu Nuwanthika Jayasena
    14 views1 page
    Black box testing evaluates the functionality of a system without seeing internal structures, using techniques like equivalence partitioning and boundary value analysis. White box testing evaluates internal structures like code statements and branches. Acceptance tests can be automated for continuous validation, though customer involvement in testing risks shifting priorities from functionality. Validation should involve both developers and users to ensure software works as intended from all perspectives.

    Original Description:

    Original Title

    Tute2

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    Black box testing evaluates the functionality of a system without seeing internal structures, using techniques like equivalence partitioning and boundary value analysis. White box testing evaluates internal structures like code statements and branches. Acceptance tests can be automated for continuous validation, though customer involvement in testing risks shifting priorities from functionality. Validation should involve both developers and users to ensure software works as intended from all perspectives.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    14 views1 page

    Tute 2

    Uploaded by

    Pubudu Nuwanthika Jayasena
    Black box testing evaluates the functionality of a system without seeing internal structures, using techniques like equivalence partitioning and boundary value analysis. White box testing evaluates internal structures like code statements and branches. Acceptance tests can be automated for continuous validation, though customer involvement in testing risks shifting priorities from functionality. Validation should involve both developers and users to ensure software works as intended from all perspectives.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    1. 2. 3. 4. 5. 6. 7. 8.

    Explain the difference between black box (functional) and white box (structural) testing techniques. Name at least three black box techniques. Use equivalence partitioning and boundary value analysis to design test cases. Recognize a state transition testing technique. Name at least three white box techniques. Understand what the meaning of statement testing and branch testing.

    9. What is the difference between black-box and white-box testing? During the software development, how can we derive black-box tests? How about white-box tests? 10. Whats the advantage if acceptance tests can be automated? 11. In XP, the customer and developers work cooperatively to specify the acceptance 12. tests. What are to pros and cons if the customer and developers work together on 13. acceptance tests 14. who should perform the validation test-the software developer or the software user?justify your answer

    You might also like