You are on page 1of 3

Module 5: Testing

Testing fundamentals Software is tested to detect and correct errors in all the stages. There are different stages of testing. They are as follows: • • • • • • • • Test planning Test case design Test execution Resultant data collection Evaluation of results Project manager, Software engineers and Testing specialist

Who dose it?

Final product of testing is test specification document Functional and structured testing Functional – black box/behavioral testing: testing are conducted at the software interface. Considers fundamental aspects of the system with little regards to the internal logic of the structure – Dose not consider internal logic – Looks from the system requirements – Checks for the module or software requirements Structured – White box/glass box testing: close examination on procedural details. Logical paths through the software and the collaborations between components are tested by providing test case that exercises specific set of condition and /or loops. – Considered internal logic – Dose not consider system requirements

– Checks the logic of the code Testing processes 1. Unit testing – module wise testing 2. Integration testing – after integration between the modules a. Top-down integration b. Bottom-up integration c. Regression testing – tested at each time a module is added in order to find out the impact of the integration in another modules d. Smoke testing – frequently testing after integration from various approach i. Benefits Integration risk is minimized Quality of end product is improved Error diagnosis and corrections are simplified Progresses is easier to accesses 3. Validation testing a. Validation test criteria – series of test that demonstrate conformity with requirements b. Configuration review – ensures that all of the elements of the software configuration have been properly developed, and cataloged and have necessary detail to bolster the support phase of the software life cycle c. Alpha and beta testing – customer level acceptance testing (alpha at developers site looking over the shoulder of customer, beta customer is active and checks for errors in requirements) 4. System testing a. Recovery testing – that force the software in variety of ways and recovery is done properly b. Security testing – will ensure the protection mechanism of the system is in proper functioning c. Stress testing – study of effect of demand or supply of recourses in abundant quantity and frequency or volume

d. Performance testing – test for run-time performance of the software with the context of an integrated systems Comparison of verification and validation techniques Verification: refers to set of activities that ensures that software correctly implements special functions Are we building the product right? Validation: refers to different set of activities that ensures the software has been built is traceable to customer requirements Are we building the right product? Reliability assessment Programmer’s productivity It is a measure of rate at which programmer develop a particular software and associated documents Programs should be simple and efficient Error removal and efficiency Debugging: • • • • • Occur as a result of testing. Once the error has been found it should be corrected. Check whether the cause of error is some effects from other parts of program Compilers and debugging tools are available It is a step wise execution of each line of code with a testing inputs