Fundamentals of Software Testing New

8/3/2019 Fundamentals of Software Testing New

1/14

SEED INFOTECH NAGPUR

A

Seminar

on

FUNDAMENTALS OF SOFTWARE

TESTING}


2/14

FUNDAMENTALS OF SOFTWARE TESTING


3/14

NEED OF SOFTWARE TESTING

What is Software?

Software is a series of instructions for the computer that

perform a particular task , called SOFTWARE.


4/14

QUALITY

Quality can be briefly defined as a degree of excellence.

Quality must be measurable and should be predictable.


5/14

SOFTWARE QUALITY

Quality software saves good amount of time and money as

software will have fewer defects , this save time during testing

and maintenance phases.

Software Quality should

Meet Customer Requirements

Meet Customer Expectations Cost to Purchase(Economical)

Time to Release(Timely release of it)


6/14

Problems of software

Defect- Defect is the variance from a desired product

attribute

Bug- A software bug may be defined as coding error that

causes an unexpected defect , flaw or fault.

Error- A mismatch between program and its specification

is an error in program.

Failure- A defect that causes an error in operation or

negatively impact a user/customer.


7/14

INTRODUCTION TO SOFTWARE TESTING

What is Software Testing?

Software Testing is process of critically evaluating software tofind bugs and fix them and to determine its current state of

readiness for release.

Testing is an art of uncovering the unknown and therefore can

be difficult to plan.

Testing is content based and risk driven.


8/14

OBJECTIVE OF SOFTWARE TESTING

Executing a program with the intent of finding an error.

To check if system meets requirements and be executed inintended environment.

To check if system does what it is expected to do.

A successful testing is one that uncovers a yet undiscovered

error.


9/14

ECONOMICS OF TESTING

Risk of under-testing is directlytranslated into system defects presentin the production environment.

Risk of over-testing is unnecessary useof valuable resources in testing systemthat may have no or few flaws thatexceed value of detecting systemdefects.

A cost effective perspective meanstesting until the optimum point isreached, which is the point where costof testing no longer exceeds the valuereceived from defect uncovered.


10/14

TEST METHODS

White Box Testing

A program level testing technique. In this technique, theresponsible people are verifying the internal structure of the

corresponding program.

Also known as Structural Testing.

Tests are logic Driven.


11/14

Black Box Testing

It is a Software level testing technique. During this test the

responsible people are validating external functionality.

Also known as Functional Testing.

Tests are data driven.


12/14

10 PRINCIPLES OF GOOD SOFTWARE TESTING

Business risk can be reduced by finding defects.

Positive and negative testing contribute to risk reduction.

Static and execution testing contribute to risk reduction.

Automated test tools can substantially contribute to risk

reduction.

Make the highest risks the first testing priority.


13/14

Make the most frequent business activities (the 80/20 rule)the second testing priority.

Statistical analyses of defect arrival patterns and other defectcharacteristics are a very effective way to forecast testingcompletion.

Test the system the way customers will use it.

Assume that defects are the result of process and notpersonality.

Testing for defects is an investment as well as a cost.


14/14

Thank you..

Documents

Fundamentals of Software Testing New