main()

{

float me = 1.1;

double you = 1.1;

if(me==you)

printf("yes");

else

printf("No");

}

 I have used following 4 types of Methodologies: 

1. Boundary value analysis   

2. Equivalence partitioning   

3. Error guessing   

4. Cause effect graphing

Integration testing is done at module level when various modules are integrated with each other to form a system or sub-system. Its main purpose is to ensure that interfaces between various modules are working properly; i.e. modules which are working individually are also working correctly together.

System testing is done on a complete, integrated system to evaluate the system’s compliance with its specified requirements. It validates that the system meets its functional and non-functional requirements.

From these definitions, it is clear that the purpose of Integration and purpose of System Testing are different. Therefore, Integration test cases focus more on the interfaces between modules (interface integrity) - the data transfer and their interaction with each other. System test cases focus on testing the product as a whole; i.e. whether the functional, non-functional requirements of the System are met or not. Since System Testing is the final phase before delivery of the product, System test cases should pinpoint configuration related errors along with testing for performance, security, reliability etc.

Glass Box (or white box) testing is the process of giving i/p to the system and checking how the system processes i/p to generate o/p

Black Box testing is the process of giving i/p to the system and checking if the system is giving correct o/p without bothering how the o/p is generated.

As we can see from the definitions, the role of black box testing is to ensure that the o/p generated is correct. And role of white box testing is to ensure that methods used to generate the o/p are correct.

Key Challenges of s/w testing:

1. Testing considered late in project

2. Requirements not testable

3. Integration is done after all components have been developed: This might result into full testing not being covered.

4. Complete testing is not possible

Testing is a process used for revealing defects in s/w and for establishing that the s/w has attained a specific degree of quality.

The s/w testing group’s main objective is to ensure that the s/w is doing what it is supposed to do as well as the s/w is not doing what it is not supposed to do. With this objective, it is clear that it is necessary to have a separate group for testing the s/w other than the group which developed it.

Also, bugs in the s/w can cause severe monetary as well as other loss to the organization. So it is important to allocate some budget for the testing group.

The main task of Software Quality Assurance Group is to examine the overall s/w development process and to create and enforce standards and methods to improve it with the goal of preventing bugs from ever occurring. With this definition, it is imperative that the QA helps an organization in continuous performance improvement and strive for perfection.

The word assurance means ‘guarantee’. So the Quality Assurance Group’s role is to guarantee that the product is of high quality. They examine the overall s/w development process and their responsibility is to create and enforce standards and methods to improve it with the goal of preventing bugs from ever occurring.

The parameters of Quality Cost are:

Speed
Accuracy
Efficiency
Performance
Customer Satisfaction