Whats comes to your mind when you hear the word Revision ?? For me it reminds me of an Engineering friend who used to revise at-least 3 times for external examination :P
So what is the connection between revision and testing ?
Before that, how many times do you test a build?? or to say how many iteration /repetition?? Do you try all combinations ? If you answer is 'till i am satisfied' and 'yes' then you need not continue reading.
Oh you cannot resist reading ? :P great, here you go. I always believe in iteration. Maybe that's why i find a lot of bugs in software. I test the same screen again and again and have a goal to find at-least 5 bugs in the screen. I try different combination, change orientation immediately after a button is tapped and so on. When I start with testing i make sure that i test the whole screen and not just a part of the screen. So when you test, keep in mind to test the application again and again until you confident that you have found all the defects. Dont be a lazy bugger. As Anne Frank quotes "Laziness may appear attractive, but work gives satisfaction"
Summarizing
1) Test the build thoroughly at-least n number of times until you are satisfied with the result
2) Try different combinations i.e try going to every returnable screen and check if proper contents are displayed.
3) Most important one: Test the whole screen and not just a part of screen.
If you find yourself bored with testing check my other post
http://qualitytesting1.blogspot.in/2013/08/things-to-do-if-you-feel-you-are-bored.html
Happy Testing :)
So what is the connection between revision and testing ?
Before that, how many times do you test a build?? or to say how many iteration /repetition?? Do you try all combinations ? If you answer is 'till i am satisfied' and 'yes' then you need not continue reading.
Oh you cannot resist reading ? :P great, here you go. I always believe in iteration. Maybe that's why i find a lot of bugs in software. I test the same screen again and again and have a goal to find at-least 5 bugs in the screen. I try different combination, change orientation immediately after a button is tapped and so on. When I start with testing i make sure that i test the whole screen and not just a part of the screen. So when you test, keep in mind to test the application again and again until you confident that you have found all the defects. Dont be a lazy bugger. As Anne Frank quotes "Laziness may appear attractive, but work gives satisfaction"
Summarizing
1) Test the build thoroughly at-least n number of times until you are satisfied with the result
2) Try different combinations i.e try going to every returnable screen and check if proper contents are displayed.
3) Most important one: Test the whole screen and not just a part of screen.
If you find yourself bored with testing check my other post
http://qualitytesting1.blogspot.in/2013/08/things-to-do-if-you-feel-you-are-bored.html
Happy Testing :)
