Manual Testing

Manual testing is the software testing which requires human input, analysis or evaluation.

Testing Methodology

White Box Testing:

Software testing approaches that examine the program structure and derive test data from the program logic. This is done under a structural testing strategy and requires complete access to the object’s structure, i.e. the source code.

Grey Box Testing:

Software testing that examines the activities of back-end components during test case execution. Two types of problems that can be encountered during gray-box testing are:

• A component encounters a failure of some kind, causing the operation to be aborted. The user interface will typically indicate that an error has occurred.

• The test executes in full, but the content of the results is incorrect. Somewhere in the system, a component processed data incorrectly, causing the error in the results.

Black Box Testing:

A testing method where the application under test is viewed as a black box and the internal behavior of the program is completely ignored. Testing occurs based upon the external specifications.

Test Phases

Integration Testing:

This phase is conducted after unit and feature testing. The intent is to expose faults in the interactions between software modules and functions. Top-down or bottom-up approaches are employed.

System Testing:

In this phase, the testing is done based on overall requirements specifications; it covers all combined parts of a system.

User Acceptance Testing:

In this phase, formal tests (often performed by a client) are done to determine whether or not a system has satisfied predetermined acceptance criteria.

Testing Approach

Interface Testing:

It is a programmable approach that provides test facilities for external interfaces and function calls. Simulation is often used to test external interfaces that currently may not be available for testing or are difficult to control. For example, hardware resources such as hard disks and memory may be difficult to control. Therefore, simulation can provide the characteristics or behaviors for specific functions.

Installation Testing:

In this approach, the installation of the software is tested to make sure that all the needed software components are installed in compliance with the software environment and time. An installation test investigates the effects on the application and on the target execution system, when installed and executed on the target system. Original installation on a clean target system, update installation on a pre-existing installation and re-installation options are explored.

Functionality Testing:

In this approach, the application of test data is derived from the specified functional requirements without regard to the final program structure.

Regression Testing:

Testing is conducted for the purpose of evaluating whether a functional improvement or repair to the program has introduced a new failure. Regression testing is accomplished through the construction, execution and analysis of product and system tests.

Performance Testing:

Testing is conducted to evaluate the compliance of a system or component with specific performance requirements.

This approach can be undertaken to:

• Show that the system meets specified performance objectives.
• Tune the system.
• Determine the factors in hardware or software that limit the system’s performance.
• Project the system’s future load-handling capacity in order to schedule its replacements.

Inter-Operability Testing:

This test approach helps to measure the ability of the software to communicate across the network on multiple machines and packages.

Exploratory Testing:

This approach of testing is to explore the unknown internal functionality of the software and involves simultaneous learning, test design and test execution.

You Should Also Check Out This Post:

More Active Posts: