Software Testing

. errors check

Check bugs

Check security

Number of lines of codes

Objectives

. uncover as many as errors as possible in a given product.

Demonstrate a given software product matching its requirement specifications.

Validate the quality of the software testing using the minimum cost and efforts.

Generate high quality test cases

Introduction: specification , functionality , performance

Konse software , software ki requirement puri hui ke nhi, speed

ERROR: IT is a human action that produce the incorrect that produce a fault.

BUG: the process of error at the time of execution of the software.

Fault: state of software caused by an error.

Failure: Deviation of the software from its expected result. It is an event.

Testing life cycle

1. project initiation.
2. System study.
3. Test plan
4. Design test case
5. Execute test case (manual/automated)
6. Report defects
7. Regression test
8. Analysis
9. Summary reports

Test plan, test case.

Verification and validation

Compare karna this is validation.

Alpha testing (within the developing organization, before market launch, It is carried out by the test
team within the developing organization.)

Beta testing ( aftermarket launch users check, It is performed by a selected group of friendly customers.)

Acceptance testing (It is performed by the customer to determine whether to accept or reject the
delivery of the system)

Performance testing (kitni ram or system pe kitna or kia asar kr rha he)

. It is carried out to check whether the system meets the nonfunctional requirements identified in the
SRS document.

Black box testing and white box testing

Testing levels

. unit testing (test modules)

. integration testing (systematic testing) types also (big bang, tip down, bottom up, mixed)

. system testing (system as a whole is tested to uncover requirement error, where verification and
validation testing occurs)

Types of performance testing.

Software testing ppt | PPT (slideshare.net)