main()

{

float me = 1.1;

double you = 1.1;

if(me==you)

printf("yes");

else

printf("No");

}

Code review is a software quality assurance activity in which one or several humans check a program mainly by viewing and reading parts of its source code, and they do so after implementation or as an interruption of implementation.

Impact Analysis is used in software testing to define all the risks associated with any kind of changes in a product being tested.

Impact Analysis is nothing but analyzing the impact of changes in the deployed product or application. It gives the information about the areas of the system that may be affected due to the change in the particular section or features of the application.

Why Impact Analysis is done :

1. It is done to understand the possible outcome of implementing the change. Inducing too much functionality into a product can reduce the overall performance of the product.

2. To identify all the files, documents and models that might have to be modified if team decides to implement the change in product

3. To estimate the effort needed behind implementing the change

4. To identify the task required to implement the change

5. It will list the dependencies on a specific element

The impact is analyzed on Requirements, Design & Architecture, impact on Test and impact on schedule.

Static Testing, a software testing technique in which the software is tested without executing the code. This Techniques provide a powerful way to improve the quality and productivity of software development by assisting engineers to recognize and fix their own defects early in the software development process.

It has two parts as listed below:

Review - Typically used to find and eliminate errors or ambiguities in documents such as requirements, design, test cases, etc.

Static analysis - The code written by developers are analysed (usually by tools) for structural defects that may lead to defects.

In this software is tested without executing the code by doing Review, Walk Through, Inspection or Analysis etc.

Hence, Error guessing is not a static software testing technique.

In software engineering, performance testing is in general, a testing practice performed to determine how a system performs in terms of responsiveness and stability under a particular workload.

Configuration management is not concerned with the choice of the hardware configuration for an application.

Configuration management is concerned with the development of procedures and standards for cost-effective managing and controlling charges in an evolving s/w system.

It includes

1)software versions maintenance

2)controlling changes in documentation

3)controlling changes to the source code

4) management activities

Sequential is the simplest file structure

A test plan is the master document that contains all details pertaining to testing of the application. Its contents include:

Testing scope - what is included and what is not included in the testing of the current project 

Assumptions - what are the assumptions that are made for this project 

Milestones - major dates like when testing is going to begin, when it is planned to end, what is the trace review date, what is the production date etc. 

Resources - the resources working on this project along with their contact details 

Defect tracking mechanism - what defect tracking tool will be used, what is the SLA for fixing Critical to Low level IRs etc. 

Test management procedures - who will be notified when there is a critical IR, what reports will be sent daily, if status calls will be held daily or weekly, where will it be held, who is required to join etc. 

Work allocation - resource distribution if more projects are being tested 

Entry and exit criterion - when can a project be accepted for testing (eg. only when smoke testing passes) and when can a project be termed as testing complete (eg. when all testcases are executed and all high level bugs are fixed)