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.
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:
Special Test Types
The following test types do not fit into particular categories and are combined with other test types.
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 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 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 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 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.
Contact KRA Systems for more information on our Software Development Services