Different Types Of White Box Testing

Different Types Of White Box Testing

Path Testing :

Taking up each and every individual path through which the flow of code taken place.

Loop Testing :

A Piece of code executing continuously until the condition becomes false and testing whether it is proper or not.

Ex: For (Loop=1; Loop<=10; Loop++)

      {

        ------

        ------

       }

Bug Life Cycle Or Defect Life Cycle In Software Testing

Bug Life Cycle Or Defect Life Cycle In Software Testing

Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing.

Click on the image for zoom view

Automation Testing Interview Questions

Automation Testing Interview Questions

1. What are principles of good testing scripts for automation?
2. What are some of the common misconceptions during implementation of an automated testing tools for the first time?
3. What are the limitations of automating software testing?
4. What are the main attributes of test automation?
5. Can test automation improve test effectiveness?

Integration Testing And Types Of Integration Testing

Define Integration Testing And Types Of Integration Testing

Integration Testing:

Combining the modules and testing the flow of data between them. Integration Testing is divided into 2 types.

• Incremental Integration Testing:

Adding the modules incrementally and checking the data flow between them. Modules are added in a sequential fashion.

This can be done in two ways 

• Top-Down Approach
• Bottom-Up approach.

Define Agile Model and its Advantages

Define Agile Model and its Advantages

Agile Model or Agile Methodology :

Agile development methodology attempts to provide many opportunities to assess the direction of a project throughout the development life cycle. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames that typically last from one to four weeks. Each iteration involves a cross functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release at the end of each iteration. Multiple iterations might be required to release a product or new features.