Software Testing

In the software development phase, testing takes up to 40 percent of the time, effort, and resources. JFsys provides world-class software testing and QA based on sophisticated diagnostic tools and proven methodology for in-depth software and system analysis.

Our testing team has the skills, tools, and techniques to assist you in deploying and maintaining State of the Art Software & Systems alike using our cost-effective offshore model.

Our testing services include:

Functionality testing

Functionality testing examines the extent to which your software, web site, or internal application meets expected functional requirements. It involves following a set of procedures designed to ensure that localized software and on-line help operates in the same manner as the original version.

Compatibility testing

Compatibility tests verify the proper functionality of features under different configurations. Configurations may include various combinations of hardware, operating systems, and application software, typically grouped into tier lists according to the likelihood of customer use. Compatibility tests are run after in-depth functionality has been verified, typically after the Functional Complete milestone. Compatibility tests are usually comprised of a subset of functional verification tests, and focus on the areas of functionality which change or are sensitive to changes in the operating environment (such as OS, driver, or application version).

Performance testing

These tests verify that the product performs within the defined performance objectives. Performance tests are run after functionality has been fully implemented, but early enough so that there’s still enough time to tune, typically between the Functional Complete and Beta milestones.

Regression Testing

Regression testing focuses on verifying that key defects have not resurfaced (particularly those legacy defects targeted for fixing in the current project) and that new defects have not been inadvertently introduced through code changes, typically covering a broad range of functionality across numerous configurations. Regression testing can be performed at any time, but is especially critical between the Beta and Code Wall milestones.

Stress & Error Testing

Stress and error testing verifies the proper functionality of features around functional boundaries, outside of normal operating conditions, and during the recovery from various error states. Often the defects found during this type of testing will have a low likelihood of occurring, so these tests are run after functionality is robust, which is typically after the Beta milestone.

Internationalization Testing

Sometimes labeled “Z Testing”, it refers to testing to see if the product works internationally, that is, it can be run on international versions of the system, responds correctly to international system settings, and functions properly for an international user.

Localization Testing

Localization testing refers to testing that the product still functions correctly after it has been transformed (NOT translated) to a different language. Localization tests verify support for localization (hard-coded strings, double-byte OS), the proper operation of locale-specific functionality (such as default paper sizes, time/date format, phone line characteristics, copy speed tariffs, etc.) and the consistency, appearance and content of localized resources (UI, help files, reports, etc.). These tests are run after UI resources have been fully localized, typically before Beta and completing upon reaching the Code Wall milestone.