Software Testing: Fundamentals

  

What is Software Testing?

Executing a program or application with the intent of finding bugs in it is called software testing. It a process of validating and verifying that a software program or application or product meets the business and technical requirements.

Methods and Types

 

Many a times we get confused as what is Testing Methods and what is Testing Types.

• Testing Method is a particular form of procedure for accomplishing or approaching testing goals.
• Testing Type is a category of testing having specific goals or characteristics.

Testing methods

Static Testing :It is a form of software testing where the software is tested without executing the code.

Examples: Code reviews, inspections and Software walkthroughs

 

Dynamic Testing: Testing the software by executing i.e. giving input values and checking if the output is as expected, which can be done manually or with the use of an automated tool.

Examples: Integration tests, System tests and Acceptance tests

 

White Box testing: It is a method of testing software that tests internal structures or workings of an application.

Example: Control flow testing, Data flow testing, Branch testing, Path testing

 

Black Box testing: It is the method of testing software that examines the functionality without knowing the internal structure of the application.

Examples: Equivalence partitioning, Boundary value analysis, Cause effect Graph, Error Guessing


Testing Types

• Functional testing :  Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered.
• Regression testing: The intent of regression testing is to ensure that a change such as enhancements/patches/configuration changes has not introduced new faults.
• Performance testing: Testing the performance of a software such as response time, resource usage and stability
• Security testing: Testing the software to verify it protects data and maintains functionality as intended
• Compatibility testing: It tests whether the application or the software product built is compatible with the hardware, operating system, database or other system software
• Smoke and sanity testing: Tests made to a systems to determine if it is ready for more robust testing
• Accessibility testing: Test with reference to users with disabilities that affect how they use the software.
• Acceptance testing:  Test conducted to determine if the requirements of a software are met as per the specifications provided.

Testing levels

• Unit testing : Test the individual unit of source code.
• Integration testing :  individual software modules are combined and tested as a group
• System testing: Testing the software as whole system (Complete integrated system)
• Acceptance testing: Tests conducted to determine if the requirements of a software are met

  

Communication:
 As a test member we think from all perspective and design test cases, the tests are executed with the intend to find bugs, if we find a bug (which is a good test) we report it to the developer and Manager. But at the same time we need to be very careful as how we react or report the defects and failures to the developers. We are pleased because we found a good bug but how will the requirement analyst, the designer, developer, project manager and customer react. Hence communication and effective polite communication is very necessary.

With Regards Vishal and friends +Vijay Rathod  +Nilesh Zade +nitin shelar  +Hrishikesh Tiwary  +Sagar Dhadge  +reegan samy  +Ashish Jethani