Web Development

Types of Software Testing Approaches

Black box testing – This kind of testing is not based on internal design or coding knowledge. These Tests are based on requirements and functionality.

White box testing – This is based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing – the most ‘micro’ scale of testing; to test particular functions or code modules. This is typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program, design and code. Not always quickly done unless the application has a well-designed architecture with tight code; it may require developing test driver modules or test harnesses.

software testing

Incremental integration testing – continuous testing of an application when new functionality is added; requires that various aspects of an application’s functionality are independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

Integration testing – Testing of combined parts of an application to determine if they are functioning together correctly. The ‘parts’ can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing – this testing is geared to the functional requirements of an application; testers should do this type of testing. This doesn’t mean that the programmers shouldn’t check that their code works before releasing it (of course, it applies to any testing stage.)

System testing is based on the overall requirements specifications; covers all the combined parts of a system.

End-to-end testing is similar to system testing; it involves testing a complete application environment in a situation that imitates real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems.

Sanity or smoke testing is typically initial testing to determine whether a new software version is performing well enough to accept it for a significant testing effort.

For example, suppose the new software is crashing systems every 5 minutes, making the systems crawl or corrupt databases. In that case, the software may not be in a normal condition to warrant further testing in its current state.

Regression testing – this is retesting after bug fixes or modifications of the software. It is difficult to determine how much retesting is needed, especially at the end of the development cycle. Automated testing tools are handy for this type of testing.

Acceptance testing – this can be said as final testing. This was done based on specifications of the end-user or customer or based on use by end-users/customers over some limited period.

Load testing – this is nothing but testing an application under heavy loads, such as testing a website under a range of loads to determine at what point the system’s response time degrades or fails.

Stress testing – the term often used interchangeably with ‘load’ and ‘performance’ testing. They were also used to describe system functional testing under cumbersome loads, heavy repetition of specific actions or inputs, the input of large numerical values, large complex queries to a database system, etc.

Performance testing – the term often used interchangeably with ‘stress’ and ‘load’ testing. Ideally, ‘performance’ testing is defined in requirements documentation or QA or Test Plans.

Usability testing – this testing is done for ‘user-friendliness’. This is subjective and will depend on the targeted end-user or customer. User interviews, surveys, video recordings of user sessions, and other techniques can be used. Programmers and testers are usually not suited as usability testers.

Compatibility testing – testing how well the software performs in a particular hardware/software/operating system/network/etc. Environment.

User acceptance testing – determining if the software is satisfactory to an end-user or a customer.

Comparison testing – comparing software weaknesses and strengths to other competing products.

Alpha testing – testing an application when development is nearing completion; minor design changes may still be made due to such testing. This is typically done by end-users or others, but not by the programmers or testers.

Beta testing is when development and testing are completed, and final bugs and problems must be found before the last release. This is typically done by end-users or others, not by programmers or testers.

Mutation testing – a method for determining a set of test data or test cases is valid or not, by intentionally introducing various code changes (‘bugs’)and retesting with the original test data/cases to determine if the ‘bugs’ are detected.

Show More

Related Articles

Leave a Reply

Back to top button