Functionality Testing

Functional testing helps to find defects early in the overall product development process. Integration testing can be included, which will assess how well different components of the product function together after they have been tested individually.

The functionality testing service we provide most often are:

• Pairwise Testing
• Acceptance Testing
• Use Case Testing
• Stress Testing
• Load Testing
• Regression Testing
• Compatibility Testing
• Interoperability Testing

Pairwise Testing

A technique designed to analyze each test case in order to arrive at the optimal number of discrete combinations to cover everything that is needed, while at the same time minimizing the effort and cost of such testing.

Acceptance Testing

This is the formal type testing which considers user needs, requirements and business processes, and is conducted to determine whether a system satisfies the acceptance criteria. It enables the users, customers or other authorized entity to decide whether or not to accept the system. The purpose is to evaluate with authority the system's adherence to the requirements.

Use Case Testing

This is a technique in which test cases are designed to execute user scenarios. The purpose of this testing technique is to do what a user would do. This testing aims to assess the tested product in a real-world environment from the user perspective. Rather than always working with a detailed set of test cases, users/testers test the product using more broadly defined scenarios.

While ad-hoc testing - one extreme case of user scenario testing - is typically "exploratory" and random, and completed only once (unless a specific defect is found), use case testing is typically a more continuous "start-to-finish" approach. The purpose of this testing is to help uncover functionality issues which might not be immediately obvious to the product developers, or to assess the product's functionality as perceived by end users/customers.

For some software developers, use case testing is considered a crucial and critical part of their overall testing approach, while others prefer to focus on other types of testing that verify the product's functionality in real-world scenarios.

Stress Testing

The objective of this type of testing is to evaluate a product or its component and how it behaves at or beyond the limits of its anticipated or specified workloads, or with reduced availability of resources such as access to memory or servers. The purpose is to test how the product behaves under limited resources.

Load Testing

Performed in an emulated real-world environment, the purpose of this testing type is to assess the product's functionality under certain "pressure" conditions (such as a networked product with 100, 1,000, or 10,000 active users), and to determine how well the product meets desired performance goals.

Regression Testing

Regression testing provides for re-testing a new release (or "drop") of the product, which contains previously fixed issues and bugs. Regression testing can also be performed between individual language versions to ensure defects from one language are fixed, or even prevented, in other language versions of the product as part of the localization testing cycle.

Compatibility and Interoperability Testing

These testing solutions are designed to verify that products will function as expected on a wide variety of hardware, software, and network configurations. Testing is performed on a specific combination of platforms or operating systems, running on defined set of hardware configurations. Compatibility testing can also be performed to assess the backward compatibility of the current version with previous legacy versions of the product, or its cooperation with other related software products.

To find out how our functionality testing solutions could help you ensure your product meets its functionality requirements, please complete the Request for Information form and we will get back to you shortly, or see other options for contacting us.