Offshore Outsourcing and Software Outsourcing Company India
 
KRA Systems

Process

   Quality     
Methodologies
Quality


Quick Links

  
Test Documents

At KRA Systems, we follow Software Quality Assurance (SQA) plan that adhere to the quality assurance needs at every phase of the software development life cycle. Our team has developed a focused quality control checklist. Our aim is to provide quantifiable and consistent results through automated processes that have been tested over time. Purpose of the SQA Plan is to establish a uniform software development process, which is applicable throughout the software development life cycle.

Our SQA Plan is a collection of the following test documents that are prepared during the respective phases of the project life cycle. They are revisited and refined as the project progresses.

Requirement Phase
Acceptance Test Document
This document compares the system to a predefined set of acceptance criteria. If the acceptance criteria are satisfied by the system, the customer will accept delivery of the system.

Analysis Phase
System Test Case Document
Requires at least one test case for each specified requirement. A traceability matrix is used to insure that requirements coverage has been satisfied. This document also covers - boundary value testing - Testing the extreme values of the equivalence classes.

Design Phase
Unit Test Plan
Unit (A unit is an abstract term for the smallest thing that can be conveniently tested) test plan details on how to exercises each software unit independently from its system. Since unit testing is usually automated this document also details on any requirements of a support harness, stubs, or drivers. The developer is responsible for doing this part of the testing.
Integration Test Plan
This document details all the test cases involved in integration of each component with the rest of the system. The developer does this part of the testing. Developer integration testing is functional testing of a component after the component has been released and the system has been built and deployed into a standard testing environment.

Tools used for Testing

KRA Systems uses WinRunner for Automated Functional testing and Compuware DevPartner Studio for Error Detection, Coverage Analysis and Performance Testing. We have standard templates for creating test plans and reporting test results.

System Test Plan

System testing compares the behavior of the test item to its specification without knowledge of the item's internal structure. System testing is also referred to as black box testing.

The following table outlines the types of System testing coverage:

Coverage Name Definition
Requirements
Requires at least one test case for each specified requirement. A traceability matrix is used to insure that requirements coverage has been satisfied.
Input Domain
Executes a function with a sufficient set of input values from the function's input domain (the set of values it can take as input parameters). Boundary Conditions are also covered in this case.
Output Domain
Executes a function in such a way that a sufficient set of output values from the function's output domain (the set of values it can return) is produced.

Special Test Types

The following test types do not fit into particular categories and are combined with other test types.

Regression Test
Exercises functionality that has stabilized (i.e. have not failed for a predetermined number of testing cycles). Once high confidence has been established for certain parts of the system, it is generally wasted effort to continue rigorous, detailed testing of those parts. However, it is possible that continued evolution of the system will have negative effects on previously stable and reliable parts of the system. Regression testing offers a low-cost method of detecting such side effects. Regression testing is often automated and focused on critical functionality. We use WinRunner to perform most of our Regression testing or a custom Test Harness is created to do the same.

Performance Test
Performance testing measures the efficiency of the system with respect to time and resources under typical usage. Performance testing is often combined with instrumentation and analysis during construction (e.g., adding trace statements with time stamps). We use Compuware DevPartner Studio to instrument our code and extract performance numbers.

Stress Test
Stress testing evaluates the performance of the test item during extreme usage patterns. Typical examples of "extreme usage patterns" are large data sets, complex calculations, extended operation, limited system resources, etc. We use custom software tools to perform stress testing based on the Project.

Configuration Test
Configuration testing evaluates the performance of the test item under a range of system configurations. Relevant configuration issues depend upon the particular system and may include platforms, peripherals, network patterns, configuration settings, etc. At KRA Systems our SQA Team has access to several hardware and software resources to perform multiple Configuration tests.

Compatibility Test
Compatibility testing is similar to configuration testing, but is focused on determining compatibility of a particular sub-system when interacting in a system with other sub-systems that can operate in that system. This is often performed on open-ended consumer systems. For consumer products, KRA recommends establishing a beta program where real users can participate in Compatibility test.

  
 
Quality Index...

  • Test Documents

  • Testing Tools

  • System Test Plan

  • Special Test Types

  •   

    Contact KRA Systems for more information on our Software Development Services


    Copyright

    www.krasystems.com