Scribd
Upload
4 views3 pages

Assignment 2

The document outlines key concepts in software testing, including the differences between verification and validation, as well as white-box and black-box testing. It discusses inspection methods, the benefits of test-driven development, and the goals of program testing. Additionally, it describes stages of testing and provides guidelines for effective testing practices.

Uploaded by

eslamosama2274
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
4 views3 pages

Assignment 2

The document outlines key concepts in software testing, including the differences between verification and validation, as well as white-box and black-box testing. It discusses inspection methods, the benefits of test-driven development, and the goals of program testing. Additionally, it describes stages of testing and provides guidelines for effective testing practices.

Uploaded by

eslamosama2274
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 3

Assignment 2:

1.Mention the difference between Verification and Validation? which one


executed first?
Verification is the process of checking that a software achieves its goal without any
bugs. It is the process to ensure whether the product that is developed is right or not. It
verifies whether the developed product fulfills the requirements that we have.
Verification is static testing.
Verification means Are we building the product right?
Validation is the process of checking whether the software product is up to the mark or
in other words product has high level requirements. It is the process of checking the
validation of product i.e. it checks what we are developing is the right product. it is
validation of actual and expected product. Validation is the dynamic testing.
Validation means Are we building the right product?
Verification comes before validation.
2. What is the difference between White-box testing and Black-box testing? In
which software testing phases, they are applicable? Why are both necessary?
Black Box Testing:

• Black Box Testing is a software testing method in which the internal


structure/ design/ implementation of the item being tested is NOT known
to the tester.
• Mainly applicable to higher levels of testing: Acceptance, System
Testing
• Done by Software Testers

White Box Testing

• White Box Testing is a software testing method in which the internal


structure/ design/ implementation of the item being tested is known to
the tester.
• Mainly applicable to lower levels of testing:Unit Testing,Integration
Testing
• Done by Software Developers
3.What is Inspection?

 These involve people examining the source representation with the aim of
discovering anomalies and defects.
 Inspections not require execution of a system so may be used before
implementation.
 They may be applied to any representation of the system (requirements, design,
configuration data, test data, etc.).
 They have been shown to be an effective technique for discovering program errors.

4. Automated test components are setup part, call part, assertion part

5. What are the three important classes of interface errors?

Misuse, Misunderstanding, Timing Errors.

6. State the Benefits of test-driven development?

• Code coverage: Every code segment that you write has at least one associated test
so all code written has at least one test.
• Regression testing: A regression test suite is developed incrementally as a program
is developed.
• Simplified debugging: When a test fails, it should be obvious where the problem lies.
The newly written code needs to be checked and modified.
• System documentation: The tests themselves are a form of documentation that
describe what the code should be doing.
7. Describe Program testing goals?
Serving as a bridge between users and development team of a product, the
ultimate goal of software testing is to troubleshoot all the issues and bugs as well
as control the quality of a resulted product.

8. What is a successful defect test?


A successful test is a test that makes the system perform incorrectly and so
exposes a defect in the system.

9. Briefly Describe the Stages of Testing?


Development testing: where the system is tested during development to discover bugs
and defects.
Release testing: where a separate testing team test a complete version of the system
before it is
released to users.
User testing: where users or potential users of a system test the system in their own
environment.

10.Testing guidelines are hints for the testing team to help them choose tests that
will reveal defects in the system. Describe these guidelines?
• Choose inputs that force the system to generate all error messages.
• Design inputs that cause input buffers to overflow.
• Repeat the same input or series of inputs numerous times.
• Force invalid outputs to be generated.
• Force computation results to be too large or too small.

You might also like