Tag Info

New answers tagged

3

Some time ago, Gregory Pope published even a longer list of root causes of bugs together with an extensive list of techniques to either detect or prevent those problems. All the material has been presented during ALM 2011 Keynote and recorded, together with slides, if you have less time, but I really recommend listening to the recorded presentation because ...


0

The goal of testing is to learn about a product. Of course it can be by finding bugs, but it can also be much more than only that. You may find that a feature is missing than a part of your users will need, that something is confusing, that your product is not usable if user have color blindness. You will discover if your product is fun or boring to use... ...


15

I work as a Manual tester on a big project. My project follows Agile methodology. I test a Web-based application. I sometimes ask my self , that am i giving any value to the stakeholders? So, the value that you are giving to stakeholders is the reduction in the amount of defects that go to production. The cost of fixing a defect drastically increases ...


3

Tester is just a label on an employee. Testing provides value. It is virtually impossible to write bug-free software, and so software that has not been tested is virtually guaranteed to be buggy. Someone needs to test it. Who tests depends on the circumstances. Some people are good at testing, and some are not. You probably want the person who tests to ...


0

Best approach would be the understand the requirement or the situation and test accordingly.


2

Check out the test heuristics cheat sheet: http://testobsessed.com/wp-content/uploads/2011/04/testheuristicscheatsheetv1.pdf This will give you some ideas of what types of things to look for when testing a given type of system. For example, when testing something with an input, do boundary testing (test the limits: what happens when you input nothing? what ...



Top 50 recent answers are included