Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1


Ratings: (0)|Views: 5 |Likes:
Published by mmalladi_1

More info:

Published by: mmalladi_1 on Jun 05, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





1.Introduction2.General Concepts of Testing3.Test Case Design Techniques 
Black box testWhite box test
4.Test Phases
Unit TestLink TestIntegration testFunction TestSystem TestAcceptance Test
5.Automated Software Testing 
Dynamic AnalysisCoverage AnalysisStatic Analysis
Software testing is arguably the least understood part of the development process as wellas most critical element of software quality assurance and represents the ultimate reviewof specification, design and code generation.Once the code of the software has been generated it is must to test it by uncovering asmaximum number of possible errors. Our goal is to design a set of test cases that havehighest probability of finding errors. During early stages of testing a software onlysoftware engineers perform all tests. However as the importance of software is increasingseparate testing specialist may become involved.Reviews and other software quality assurance activities can uncover errors, but they arenot sufficient. Every time a program is executed the client test it, therefore we have to testthe program with the specific intent of finding and removing as many as errors as possible. To find the highest possible number of errors, tests must be conductedsystematically and designed using standard techniques.A series of test cases to test both internal logic and external logic is designed anddocumented using disciplined techniques and expected results are also defined and actualresults are recorded to compare with the expected results.When we begin testing, we should change our point of view and try hard to break thesoftware design test cases in a disciplined fashion and review the test cases we do createfor thoroughness.In the end it seems like software testing is destructive activity but in true meanings it isconstructive and requires a great deal of attention.
During testing the software engineering produces a series of test cases that are used to“rip apart” the software they have produced. Testing is the one step in the software process that can be seen by the developer as destructive instead of constructive. Softwareengineers are typically constructive people and testing requires them to overcome preconceived concepts of correctness and deal with conflicts when errors are identified.
Testing is the process of executing program(s) with the intent of finding errors, rather than (a misconception) of showing the correct functioning of the program(s). Thedistinction may sound like a matter of semantics, but it has been observed to have profound effect on testing success. The difference actually lies on the different psychological effect caused by the different objectives: If our goal is to demonstrate thata program has no errors, then we will tend to select tests that have a low probability of causing the program to fail. On the other hand, if our goal is to demonstrate that a program has errors; our test data will have a higher probability of finding errors.Specifically, testing should bear the following objectives:(a) To reveal design errors;(b) To reveal logic errors;(c) To reveal performance bottleneck;(d) To reveal security loophole; and(e) To reveal operational deficiencies.All these objectives and the corresponding actions contribute in increasing quality andreliability of the application software.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->