At Opportune, software testing is a valued expertise. Our expert software test engineers who follow an established testing process and utilize testing tools and methodologies. Our testing Organization can delivers high-quality, cost-effective testing services to get the defects out of your applications, and ensures always-on-schedule final release. We take advantage of  our testing methodology outstanding and testing tools to serve your testing needs in all aspects from test planning , test case designing and test environment setting up to test execution and project management.

How we do it

We divide the general testing process into four separate stages, each with its own distinctive focus.

1.Project Definition

Define the testing scope, detailed requirements, budget and schedule with the client. Make sure that everything crucial to the project's success is discussed and agreed on by both parties. We can propose a feasible testing plan to our client.

2.Project Preparation

Prepare everything from setting up the testing environment to forming a team with the right skill sets, from penning down the milestone and report mechanics to clarifying expectations for each tester and their evaluation methods. All these measures ensure that the project is implemented with clear targets and sufficient resources. Risk analysis is also included at this stage

3.Project Execution

Testers and test leads execute test cases in both a meticulous and exploratory manner. Besides the regular testing laid out according to the scripts, our experienced testers also design and run ad hoc testing to discover important defects

4.Project Review

This is indispensable to continually improving the services we offer our clients, as our long-term commitments call for better performances with each project, saving our client precious time and reducing costs, and indeed, sharpening their competitive edge. The project review is something that requires serious and thorough participation from our whole team as well as our clients

Service offerings

We provide comprehensive testing services from software to website to mobile device testing. Please take a look at the following list of testing types:

Function testing

Functionality testing examines the extent to which your hardware, 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 operate in the same manner as the source version.

Compatibility Testing

Compatibility tests verify the proper functionality of features under different configurations; configurations may include various combinations of hardware, operating system, and application software, typically grouped into tier lists according to the likelihood of customer use. Compatibility tests are run after in-depth func[FS:PAGE]tionality has been verified, typically after the Functional Complete milestone. Compatibility tests are usually comprised of a subset of functional verification tests, focused on 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 & Load 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.

Technologies and tools

Testing Tools

Apart from industry-standard tools, such as Silk Test, WinRunner and Load Runner,
we develop our own tools to meet the specific needs of one type of testing.

Networks

We have a solid knowledge of networks. Our testing team houses a sophisticated
network for various network-based tests.