software testing 6th sem ise notes please

please visit Software Testing Note Book

Manual Testing Guide

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

Software Testing are contains two types:

1) Manual Testing and,
2) Automation Testing

Manual Testing:

Manual testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases

Software Testing Definition: Testing is the process of executing a program with the intention of finding errors.

Drawbacks of Manual Testing

(i)Time consuming.
(ii) More resources required.
(iii)Human Errors
(iv)Repetition of the Task
(v)Tiredness
(vi)Simultaneous auctions are not possible (Parallel)
Software Engineering: Software Engineering is the establishment and use of sound engineering principles in order to obtain economically software that is more reliable and works efficiently on real machines.

Reviews during Design:

After the completion of analysis of customer requirements and their reviews, technical support people (Tech Leads) concentrate on the logical design of the system. In this every stage they will develop HLDD and LLDD.

After the completion of above like design documents, they (tech leads) concentrate on review of the documents for correctness and completeness. In this review they can apply the below factors.

Is the design good? (understandable or easy to refer)
Are they complete? (all the customer requirements are satisfied or not)
Are they correct? Are they right Requirements? (the design flow is correct or not)
Are they follow able? (the design logic is correct or not)
Does they handle error handling? ( the design should be able to specify the positive and negative flow also)

Underlying Principles

Terminology

The IEEE standard defines a failure as the external, incorrect behavior of a program [IEEE, 1996]. Traditionally,
the anomalous behavior of a program is observed when incorrect output is produced or a runtime
failure occurs. Furthermore, the IEEE standard defines a fault as a collection of program source code
statements that causes a failure. Finally, an error is a mistake made by a programmer during the implementation
of a software system [IEEE, 1996].2 The purpose of software testing is to reveal software
faults in order to ensure that they do not manifest themselves as runtime failures during program usage.
Throughout this chapter, we will use P to denote the program under test and F to represent the specifi-
cation that describes the behavior of P.
3 We say that a program’s execution is correct when its behavior
matches the functional and non-functional requirements specified in F [Sommerville, 2000]. Normally,
the program under test will operate in an environment that might include Java virtual machines, device
drivers, operating systems, databases, and a host of other environmental factors [Whittaker, 2000, Whittaker
and Voas, 2000]. The majority of the testing theory and the practical testing techniques discussed
in this chapter disregard the environment of a software system and simply focus on the source code of P.
However, some of the new approaches to software testing that are described in Section 3.9 do address the
testing of an application and its interaction with its environment.