Functional Testing





QA Valley performs Functional Testing on systems and applications that are newly developed or enhanced with the explicit objective to ensure that all Business Requirements and Systems Specifications are satisfied. The intent is to establish that transactions are perform in a manner that is coherent with User Expectations, and to effectively document all defects and gaps that may hinder a successful release. This type of testing is performed strictly from the users’ perspective by emulating the actions and behaviors to which the system will be routinely exposed.

The System Specifications or Business Requirements are utilized as the cue that drives the Functional Testing process. Transactions are entered with specific inputs, and the resulting outputs are evaluated to establish accuracy and completeness. These are Black Box Scenarios to verify that the individual requirements are accurately fulfilled by matching inputs and outputs to establish validity. The process is repeated for each individual requirement outlined in the System Specifications, and may be storyboarded or recorded to prove completeness.

QA Valley compiles a portfolio of Function Test Cases that are reflective of the System Specifications or Business Requirements. These Test Cases are grouped according to the functions they support, and are executed in sequence according to a Function Test Plan. Functions that pass all corresponding test cases are flagged as complete, and are marked for subsequent user acceptance. In most cases there are interdependencies among functions which demands that prerequisite functions be flagged as complete before dependent functions can be validated.

Defects and Failures are logged into a common QA Valley Defect Tracking System which is used for tracking numerous test parameters such as Tester, Test Case, Build, Transaction Screen Capture, Defect, Severity, and many more. Tracking may also occur by utilizing client specific systems but observing the same rigid practices in Functional Testing enforced by QA Valley. Transaction screen sequence and video capture are generally stored separately but are linked to the associated defects so that users and developers can easily locate for playback.