GENERAL TESTING PROCESS Confidential Focal3 Softw are Pvt Ltd F3 - PDF document

F3 _ Doc_ 0 0 5 VER4 .0 Page 1 of 6 GENERAL TESTING PROCESS Confidential Focal3 Softw are Pvt Ltd

F3 _ Doc_ 0 0 5 VER4 .0 Page 2 of 6 Introduction The purpose of testing is to verify the software and remove defects. Testing verifies the code against the requirements and the design to ensure that the requirements are implemented. Testing also identifies problems and defects that are corrected and tracked to closure before product delivery. Testing should also validate that the software operates appropriately in the intended environment. Test Cycle The following is an outline of the planned testing process for all Focal3 software development projects. It is important to note that throughout each cycle, code reviews and inspections will take place appropriately. Any parts of code not testable through the black box / interface testing methods will be exercised by test harnesses written by QA team members and approved by the Project Manager, Development and QA team leaders. Planned Test Cycles • Unit Testing • Cluster Testing • Thread Testing • Stress/ Performance Testing • Acceptance Testing Unit Testing Cycle This will involve the white box and black box methods of testing using test harnesses to locate defects within each class of the system. The outputs expected from the inputs entered will be determined from the requirements specification document. Cluster Testing Cycle The main focus will be with interface testing the parameter and procedural interfaces, yet minimal black box and white box testing will occur at this stage, the outputs expected from the inputs will be determined from the requirements specification document. Thread Testing Cycle Interface testing will take up the majority of work hours with a strong focus on the testing of the synchronized classes and message passing interfaces (anticipated). Thread testing will be repeated on the entire integrated system once all sub-systems are free of interface errors. Confidential Focal3 Softw are Pvt Ltd

F3 _ Doc_ 0 0 5 VER4 .0 Page 3 of 6 Stress/ Perform ance Testing Cycle The idea of this phase is to see how quickly and reliably the system operates under increasing loads and users. The aim is to identify possible problem areas that can be fixed in order to fine-tune the system. Acceptance Testing Cycle This will be the final phase of testing. It will only take place after all the previous test phases have been completed and the system is error free within the development environment. The purpose of this test phase is to test the performance of the system in real-time working environment with real users. This is done in order to find errors not anticipated by the developers or QA staff. Code Inspections During the regular code inspections and reviews, particular attention will be paid to: • The use of well defined exception handlers, instead of using the default. • Use of product on all platforms. • Use of comments. • Maintainability of code. • "Magic Numbers" included for no apparent reason. • Loops with multiple exit or entry points. • Unreachable code. • Memory leaks. • Variables used without initialization. • Variables declared but never used. • Possible array bound violations. • Uncalled functions. • Use of Public, Private, Protected and Published sections within classes. Confidential Focal3 Softw are Pvt Ltd

F3 _ Doc_ 0 0 5 VER4 .0 Page 4 of 6 Test Plans/Scripts For each class, cluster of class, sub-system and the entire system, a test plan/ script document will be written which has the following sections and content: Test Conditions A brief explanation of the following information that contains the conditions in which the software tests will be conducted: o Pre-Test Background Brief explanation of what is expected to have occurred before the testing of the software begins. For example, "It is assumed that the software has been put through ad-hoc testing performed by the developer, and can run without any obvious fatal errors". o Test Site Where the tests are to be performed, ie "The tests are being conducted in the Focal3, Wilcrest Point office, Trivandrum, India". o Test Personnel The number and name of the persons involved of the testing of the software in question. o Test Environm ent The hardware and software specifications in which the tests will be conducted on. o Test Constraints Anything within the test environment that may inhibit the quality or productivity of the tests. o Test Methodologies What style of testing will be used, ie. Black-Box testing o Test Tools Any software tools that may be used to help test the software, ie. WinRunner, Loadrunner etc. o Test Com pletion Criteria The criteria needed for the software to pass the testing process. Confidential Focal3 Softw are Pvt Ltd

F3 _ Doc_ 0 0 5 VER4 .0 Page 5 of 6 Test Overview A brief introduction that explains the content of the following three sub-sections that are: • Functional aspects that need to be tested • Non-Functional aspects that need to be tested • Test sections and example tests Breakdow n of Functional Aspects A description/ list of every aspect of the functional points of the software to be tested. Breakdow n of Non-Functional Aspects A description/ list of every aspect of the non-functional points of the software to be tested. Test Sections and Exam ple Tests Description of the formulated test sections and sample tests that will be conducted within those test sections in table format. Functional Tests Test Section Exam ple Tests I nvolved Non-Functional Tests Test Section Exam ple Tests I nvolved Confidential Focal3 Softw are Pvt Ltd

F3 _ Doc_ 0 0 5 VER4 .0 Page 6 of 6 Functional Tests Test - Section Nam e ( ie. Exception Handling) A brief description of the purpose of the test section. Functional Test I nputs An outline of the types of inputs entered by the tester or by the test harness. Functional Test Outputs An outline of the outputs expected from the software for the types of inputs entered. Also include any recording devices which will monitor the test process. If this includes files, list the names of the files that record information. Procedures Numbered detailed tests, their steps and expected results. The number of tests depends on the size of the software to be tested. With each of the tests (each number within this section), copy the following to the end of each number: Pass: Fail: Refer to: Non-Functional Tests Review ( section of softw are to review ) A brief description of the purpose of the review section. Procedures A numbered list of things to review and report personal opinions on. ie background color of the UI or color in client logon dialog box etc. Confidential Focal3 Softw are Pvt Ltd