| Business Availability & Continuity Services |
 |
|
|
| |
 |
|
|
|
|
| |
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
What Functional
Functional Testing is conducted to evaluate the compliance of a system or component with specified functional requirements and corresponding predicted results. Functional Testing ignores the internal mechanism or structure of a system or component and focuses on the outputs generated in response to selected inputs and execution conditions. Through Functional testing, one checks the program against every claim made in a reference document, such as a design specification, a requirements list, (and for UATs, a user interface description, a published model, or a user manual). This involves testing of the product's user interface, APIs, database management, installation, networking, etc. Such tests are executed and implemented against different target of tests, including units, integrated units, module(S) application(s), and system(s).
User Acceptance Test (UAT)
A User Acceptance Test is conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. A User Acceptance test is performed purely from the application user’s perspective. Though a UAT is similar to a Functional test, a UAT differs in the depth of testing that is executed onto an application. A UAT would confirm that various outputs expected from the application are displayed, but does not check the authenticity of the output, and whether it confirms to the required result.
Why
Today’s enterprises are faced with deploying and managing increasingly complex applications that are essential to the business for generating revenue and managing customer satisfaction. Ensuring that these applications and their underlying infrastructure perform adequately under anticipated conditions and meet business needs is crucial to ensure a company’s long-term revenue potential. Many enterprises deploy applications only to find that they perform poorly or fail to scale to the required degree.
How we do it at Our Test Labs?
Faced with the reality of having to do more with less, juggle multiple projects and manage diverse and distributed project teams, most organizations find it practically impossible to manage a full fledged test team in-house. Most projects are under tremendous time pressures and hence only do testing that can fit those time scales rather than ensuring that the breadth & width of the tests is optimal.
At Omnitech, we look beyond documentation for problems in the specification. We profess that the most informative tests in a well-specified product are often the ones that explore ambiguities in the specification or examine aspects of the product that were not well-specified, in addition to what the requirement specification recites.
As for regression testing, the Test Planning group at Omnitech plays a major role during iterations. Each documented change is studied carefully while preparing for a regression test. Consequence of each change, direct, indirect or consequential is closely monitored for functionality. A test build / version control mechanism employed for the purpose of reporting helps coders pinpoint errors in the code with precise accuracy, thus facilitating quicker remedial action.
Functional / Regression / UAT testing may require domain knowledge. Domain specialists and project heads work in close coordination with each client while preparing test plans. Each testing team member is intensely trained to ensure sufficient understanding of the functionality of the application before testing commences. This ensures that testing is not a mechanical process but a fully understood activity. |
| |
|
