Embed Doc
Copy Link
Readcast
Collections

1
CommentGo Back

Download

OFTWARE

ESTING

IntroductionDefinitionNeed for TestingMisunderstanding about Testing Testing Techniques Types of TestingLevels of TestingFinal version of Testing- Alpha Testing- Beta TestingWhen to stop Testing?Conclusion

Compiled by

V. Raj Kumar

oftware

esting

Introduction:

“Testing is a process of planning, preparing, executing and analyzing, aimed atestablishing the characteristics of an information system, and demonstrating thedifference between the actual status and the required status.”A primary purpose for testing is to detect software failures so that defects may beuncovered and correctedSoftware bugs will almost always exist in any software module with moderatesize: not because programmers are careless or irresponsible, but because the complexityof software is generally intractable -- and humans have only limited ability to managecomplexity.

Main objective



Testing is a process of executing a program with the intent of finding an error.



A good test case is one that has a high probability of finding an as yet undiscoverederror.



A successful test is one that uncovers an as yet undiscovered error.



Identifies defects before software deployment



Reduces incompatibility and interoperability issues



To reduce the cost of rework by detecting defects at an early stage.

Role of Testing

Primary



Determine whether system meets specifications



Determine whether system meets needsSecondary



Instill confidence



Continuously improve the testing process

Definition



Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies specified requirements -(IEEE 83a)



A process of demonstrating that errors are not present?



A way of establishing confidence that a program does what it is supposed to do?

Need for Testing?

A study conducted by NIST in 2002 reports that software bugs cost the U.S. economy$59.5 billion annually.Testing reduces the level of uncertainty about the quality of a system.



Quality Control:

Mechanism to ensure that the required quality characteristicsexist in the finished product.



Quality Assurance:

Ensures that the quality management procedures work.



Verification

refers to the set of activities that ensure that software correctlyimplements a specific function, imposed at the start of that phase.



Validation

refers to the test phase of the life cycle which ensures that the end product meets the user’s needs.Verification: Have we built the software right (i.e., does it match the specification?)? It is process based.