Testing Techniques

**Software testing (as per IEEE):-** is the process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs) and to evaluate the features of the software item.

There are two types of techniques
A Static testing
B Dynamic Testing

Techniques used in Static Testing:-
Static Testing is a technique in which the software is tested without executing or running the code. It vary from Informal to Formal Informal reviews:- come are little documented or not documented. Formal Review:- It follow process of six steps

i) Planning:- It begins with a 'request for review' by the author to the moderator (or inspection leader). A moderator is often assigned to take care of the scheduling (dates, time, place and invitation) of the review.
ii) Kick-off:- The goal of this meeting is to get everybody on the same wavelength the result of the entry check and defined exit criteria are discussed in case of a more formal review.
iii) Preparation:- The individual participants identify defects, questions and comments, according to their understanding of the document and role. All issues are recorded, preferably using a logging form.The annotated document will be given to the author at the end of the logging meeting.
iv) Review meeting:- The meeting typically consists of the following elements (partly depending on the review type): Logging phase, Discussion phase and Decision phase.
v) Rework :- Based on the defects detected, the author will improve the document under review step by step. It is the author's responsibility to judge if a defect has to be fixed.
vi) Follow-up.:- The moderator is responsible for ensuring that satisfactory actions have been taken on all (logged) defects, process improvement suggestions and change requests.

**2. Informal Review:-** This is one of the type of review which doesn't follow any process to find errors in the document. Under this technique , you just review the document and give informal comments on it

**3. Walkthrough:-** The author of the work product explains the product to his team. Participants can ask questions if any. Meeting is led by the author. Scribe makes note of review comments

**4. Technical / Peer Review:-** A team consisting of your peers, review the technical specification of the software product and checks whether it is suitable for the project. They try to  find any discrepancies in the specifications and standards followed. This review concentrates mainly on the technical document related to the software such as Test Strategy, Test Plan and requirement specification documents.

**5. Inspection:-** The main purpose is to find defects and meeting is led by trained moderator. This review is a formal type of review where it follows strict process to find the defects. Reviewers have checklist to review the work products .They record the defect and inform the participants to rectify those errors

**7. Data-flow testing:-** uses the control flowgraph to explore the unreasonable things that can happen to data (i.e., anomalies).

**8. Static code Review:-** This is systematic review of the software source code without executing the code. It checks the syntax of the code, coding standards, code optimization, etc. This is also termed as white box testing .This review can be done at any point during development.