Path and Branch Coverage

Path and Branch Coverage Coverage has been around for a long time but is often misunderstood. In the realm of unit testing, it is critical to understand, especially if you want to have a solid unit testing strategy. So, let's start with the basics. Code coverage is a way to measure the level of testing you've performed on...

Read more »

Code Coverage

Introduction Code coverage analysis is the process of: Finding areas of a program not exercised by a set of test cases, Creating additional test cases to increase coverage, and Determining a quantitative measure of code coverage, which is an indirect measure of quality. An optional aspect of code coverage analysis is: Identifying...

Read more »

White Box Testing Technique

Data-Flow Analysis Data-flow analysis can be used to increase program understanding and to develop test cases based on data flow within the program. The data-flow testing technique is based on investigating the ways values are associated with variables and the ways that these associations affect the execution of the program. Data-flow analysis focuses on occurrences of variables, following paths from the definition (or...

Read more »

Ad-hoc Testing

This type of testing is done without any formal Test Plan or Test Case creation. Ad-hoc testing helps in deciding the scope and duration of the various other testing and it also helps testers in learning the application prior starting with any other testing. It is the least formal method of testing. One of the best uses of ad hoc testing is for discovery. Reading the requirements or specifications (if they exist)...

Read more »

Beta Testing

A product's beta is an officially released version of a product which includes most of the product's functionality. The beta version is intended for external testing of the product in order to identify configurations that cause problems, as well as collect requirements and suggestions from users. Before its official release, a beta version ALWAYS undergoes a full cycle of internal testing, after which the application is...

Read more »

Alpha Testing

Before any software product can be released it must be tested. Typically a formal test strategy is planned and executed on the software before it can be considered for release. Often after the formal phases of testing have been completed, additional testing is performed called Alpha and Beta testing. Alpha testing is done before the software is made available to the general public. Typically, the developers will perform...

Read more »

Entry and Exit Criteria

The Entrance Criteria specified by the system test controller, should be fulfilled before System Test can commence. In the event, that any criterion has not been achieved, the System Test may commence if Business Team and Test Controller are in full agreement that the risk is manageable. * All developed code must be unit tested. Unit and Link Testing must be completed and signed off by development team. * System...

Read more »

Visual testing

Visual testing The aim of visual testing is to provide developers with the ability to examine what was happening at the point of software failure by presenting the data in such a way that the developer can easily find the information he requires, and the information is expressed clearly. At the core of visual testing is the idea that showing someone a problem (or a test failure), rather than just describing it, greatly increases...

Read more »

Cyclomatic Complexity

Software metrics often receive negative criticism, as they are viewed as an exact science, uniformly applicable to all scenarios. True, software metrics are an unbiased, objective measurement of a particular aspect of code; however, a particular metric's applicability to a domain is usually subjective. For instance, highly coupled code may have been intentionally designed that way for performance reasons; consequently, a...

Read more »

Error Guessing

Error guessing is testing technique which used for creating test cases used to find bugs. Error guessing technique is useful if the resource that will be creating the test cases will be having prior knowledge about testing or about the business or about the application. In error guessing tester uses intuition, instincts to find out in what all situation a software might fail. It is an ad hoc method to identify bugs depending...

Read more »

Boundary Value Analysis

Boundary Value Analysis is a Blackbox Testing Technique. It makes use of the fact that the inputs and outputs of the component under test can be partitioned into ordered sets with identifiable boundaries. Values in the same set will be treated in the same way. Test values are chosen that are just inside, on and just outside the boundaries. ...

Read more »

Testing Techniques

Testing TechniquesTesting techniques refer to different methods of testing particular features a computer program, system or product. Each testing type has its own testing techniques while some techniques combine the feature of both types.Black box testing techniques:* Graph Based Testing Methods* Error Guessing* Boundary Value analysis* Equivalence partitioning* Comparison Testing* Orthogonal Array TestingWhite box testing...

Read more »

Bug Report

Anybody who has written software for public use will probably have received at least one bad bug report. Reports that say nothing ("It doesn't work!"); reports that make no sense; reports that don't give enough information; reports that give wrong information. Reports of problems that turn out to be user error; reports of problems that turn out to be the fault of somebody else's program; reports of problems that turn...

Read more »