Software Testing Methodologies and Implementations

Short presentation on different software testing methodologies and how to implement them.

Transcript

1. –Michael Stahl’s derivative of Murphy’s Law “Irreproducible bugs become highly reproducible right after delivery to the customer.”
2. What I will be covering Ad-hoc Testing Functional Testing Performance Testing Automated Testing Why bugs appear What can we do to implement these processes
3. Text Ad-hoc What is it?
4. Ad-hoc testing is a software testing method that doesn’t include any planning or documentation Pros As the method follows no rules, testers can be more creative Defects can be found which can often be missed with a documented process Provides quick results Cons Success depends on the creativity of the tester No formal planning or documentation Defects can be hard to reproduce as there are no test cases
6. Text Functional Testing
7. ISTQB defines Functional Testing as ‘Testing based on an analysis of the specification of the functionality of a component or system.’ Typically this is achieved through the following steps Identify functions that the software needs to perform. These come from user/business requirements. Create test and input data based on these functions Determine what the output should be based on these functions Compare actual and expected results Highlight any discrepancies
8. These steps come in the form of a Test Plan Each test in the Test Plan is called a Test Case If a Test Case fails due to a bug, this is flagged in the test plan and the bug is logged in the ticket system. Pros Allows for a more precise and structured way to test resulting in increased efficiency Increased efficiency means higher bug detection Cons Time-consuming
10. Text Performance Testing
11. Performance Testing is a means of testing software stability and responsiveness under a certain workload 4 Main types of performance testing Load Testing Stress Testing Endurance Testing Spike Testing
12. Tools and tips! There are many performance testing tools out there Google PageSpeed Yahoo! YSlow WebLoad LoadRunner Chrome Developer Tools There is no best tool! Test environment should be as close as possible to production Performance tests need to be run over and over to establish a benchmark
13. Text Automated Testing
14. Automated testing involved automating parts of the testing process via the creation and execution of test scripts Test Scripts are written in a programming language such as Ruby or Python Testing frameworks are available such as Rspec They allow for aspects of the testing process to be run automatically Help speed up testing
15. Live Demo
16. So why do bugs appear? Undocumented change requirements Programming errors…we all do it! Miscommunication Time pressures
17. How can we implement these methods? We are! Introduction of a Testing Policy Establish a QA Team Proposal of an Advanced Testing App
18. –Jake Black “Irreproducible bugs become highly reproducible right after delivery to the tester.”