Software Testing: A Self-Teaching Introduction
Book PrefaceSoftware Testing: A Self-Teaching Introduction
Testing is the process of executing the program with the intent of finding faults. Who should do this testing and when should it start are very important questions that are answered in this text. As we know software testing is the fourth phase of the software development life cycle (SDLC). About 70% of development time is spent on testing. We explore this and many other interesting concepts in this chapter.
1.1.THE TESTING PROCESS
Testing is different from debugging. Removing errors from your programs is known as debugging but testing aims to locate as yet undiscovered errors. We test our programs with both valid and invalid inputs and then compare our expected outputs as well as the observed outputs (after execution of software). Please note that testing starts from the requirements analysis phase only and goes until the last maintenance phase. During requirement analysis and designing we do static testing wherein the SRS is tested to check whether it is as per user requirements or not. We use techniques of code reviews, code inspections, walkthroughs, and software technical reviews (STRs) to do static testing. Dynamic testing starts when the code is ready or even a unit (or module) is ready. It is dynamic testing as now the code is tested. We use various techniques for dynamic testing like black-box, gray-box, and white-box testing. We will be studying these in the subsequent chapters.
1.2.WHAT IS SOFTWARE TESTING?
The concept of software testing has evolved from simple program “check-out” to a broad set of activities that cover the entire software life-cycle.
There are five distinct levels of testing that are given below:
a.Debug: It is defined as the successful correction of a failure.
b.Demonstrate: The process of showing that major features work with typical input.
c.Verify: The process of finding as many faults in the application under test (AUT) as possible.
d.Validate: The process of finding as many faults in requirements, design, and AUT.
e.Prevent: To avoid errors in development of requirements, design, and implementation by self-checking techniques, including “test before design.”
|Download Ebook||Read Now||File Type||Upload Date|
|Download here||Read Now|
|EPub, PDF||February 8, 2019|
Do you like this book? Please share with your friends, let's read it !! :)How to Read and Open File Type for PC ?