1. Testing, Testing & Testing - By M.D.ACHARYA QA doesn't make software but makes it better

2. Myths Vs Facts Myths : –Developers require more skills in comparative to QA. –Development needs more effort then testing. Facts: –Tester needs to think one step ahead then developers to breaks their code. –Testing is more creative than development because you need to be creative to become destructive :)

3. Software Testing Software Testing is a process of evaluating a system by manual or automatic means and verify that it satisfies specified requirements or identify differences between expected and actual results

4. Observations about Testing “Testing is the process of executing a program with the intention of finding errors.” “Testing can show the presence of bugs but never their absence.”

5. Good Testing Practices - “Assign your best people to testing -Ensure that testability is a key objective in your software design -Never alter the program to make testing easier -Testing, like almost every other activity, must start with objectives

6. Levels of Testing - Unit Testing -Integration Testing -Validation Testing -Regression Testing Alpha Testing Beta Testing -Acceptance Testing

7. Unit Testing - Algorithms and logic -Data structures (global and local) -Interfaces -Independent paths -Boundary conditions

8. Why Integration Testing Is Necessary - One module can have an adverse effect on another -Sub functions, when combined, may not produce the desired major function -Individually acceptable imprecision in calculations may be magnified to unacceptable levels

9. Top-Down Integration 1. - The main control module is used as a driver, and stubs are substituted for all modules directly subordinate to the main module. 2.Depending on the integration approach selected (depth or breadth first), subordinate stubs are replaced by modules one at a time.

10. How to do Testing and it's life cycle Unit Testing Sanity Testing Functional Testing Integration Testing Regression Testing Stress Testing Load Testing Performance Testing Solution Testing How to do testing??

11. 1 st Cycle - Unit and Sanity Testing Unit Testing: It covers testing on a specific part of code perform by developers. Sanity Testing: It's very basic level testing done by QA after fixing some bug. Basic Cleaning of Bugs

12. 2 nd Cycle - Functional, Integration and Regression Testing Functional Testing: Focus majorly on specific functionality of component. Integration Testing: To check, how that functionality work after integrating with some other functionality. Regression Testing: To check older functionality after integrating new functionality. Complete Mix Testing

13. 3 rd Cycle - Stress, Load and Performance testing Performance Testing: It means how best something performs under a given benchmark. Load Testing: It is also performance testing but under various loads. Stress Testing: It is performance under stress conditions.

14. 4 th Cycle- Solution or End to End Testing It's done in a completely emulated customer setup, involving multiple products and most of the time multiple vendor products. If it's done at the customer site then it's also called as pre-production testing.

15. How to Plan and Organize Test case Project Test plan Functionality Test cases

16. Verification Vs Validation Verification:  Are we building the product right?  The software should conform to its specification. Validation:  Are we building the right product?  The software should do what the user really requires

17. Common tools for Testing Siebel: Bug tracking tool from Oracle. Rational Robot: Load testing tool from IBM. Mercury winrunner: Performance testing tool from Hp SIPP: For Sip protocol testing. Ethereal: For sniffing packets. Test complete: For GUI automation.

18. THANKYOU