my testing adventures - effectiveness

If you check the date of recent posts , you will see that this is the third post today. My colleague smiles - it is friday, too difficult to work when you know three days of rest are waiting ahead.

Today is a reading day, so the next thing I found in one blog - testing metrics. The authour lists a few of them. the most interesting for me - "Number of customer reported Bug - As a measure of testing effectiveness".

Ok. The effectiveness of testing.... Let's see - my first project here, small and my independent work as a tester. pilot project :)
  • Total issues registered for the project - 164;
  • Total bugs - 119;
  • Client reported issues - 27;
  • Client bugs - 21;
  • Some of them seem quite 'strange' for me and I simply can not call them "bug", so will leave - 10 bugs with low priority.

So, what we have for my testing effectiveness? 10 of 119? Less than 9 percent.

What is the 'normal' and accepted rate? Can not find anything on that topic in the web for a moment.

Comments

Unknown said…
Hi,

I have 3+ years experience in manual testing,now i am looking for the change.Kindly send if any requirement in detail.
Mail id : joseph_stanleyx@yahoo.co.in
12:39 AM
Post a Comment

Popular posts from this blog

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Read more

tester's day!

Happy testers day! Top 24 replies by programmers when their programs don't work: 24. "It works fine on MY computer" 23. "Who did you login as ?" 22. "It's a feature" 21. "It's WAD (Working As Designed)" 20. "That's weird..." 19. "It's never done that before." 18. "It worked yesterday." 17. "How is that possible?" 16. "It must be a hardware problem." 15. "What did you type in wrong to get it to crash?" 14. "There is something funky in your data." 13. "I haven't touched that module in weeks!" 12. "You must have the wrong version." 11. "It's just some unlucky coincidence." 10. "I can't test everything!" 9. "THIS can't be the source of THAT." 8. "It works, but it's not been tested." 7. "Somebody must have changed my code." 6. "Did you check for a virus on your system?...
Read more