Hi Readers,
Its good to be back after so many days!
Today I want to discuss something on a common problem in Testing world. Time v/s Test Coverage. I am sure every Tester comes across this situation in his career.
Its very obvious that a proper testing needs a proper time. But sometime the user needs the product earlier then even the user expected. What do we do on such cases? We can't handover a buggy application to the user!
In my Testing Life the following is what I have observed and have followed:
1. Test the application as much as possible.
You are a Tester. You don't let the application be buggy when it reaches Customer, even if you have less time. Give your best and test the application as much as possible. As a Tester we always believe that this application till have defects. Then this is the time to find as much as bug we can!
2. Exploratory Testing is your best bet in this situation.
Exploratory Testing is the way though which we don't test in a scheduled way. We test and we find. So when we have less time, we can prioritize our test and test the application by exploring. Do some random testing and check how application reacts to you.
3. Don't forget to cover the major functionality of the application.
When time is our concern, its the major functionality that we need to focus on. I have seen testers doing very good testing, but only to know that this functionality is not a major focus for this sprint. And the output is several major functionality for the sprint remained not properly tested. Hence its the major functionalities that we can focus on when we have to deliver in a tight schedule.
4. Discuss with the user about there usage preferences.
Its always the end user who is going to use the application. The best guide for you can be the business users or end users in such cases. Talk to them, understand what exactly they are expecting from the application from this remaining time? What they want to be tested on priority. Give your inputs to them on applications (what do you think might be the priority, how we can do a better testing in stipulated time). Remember that the business user or end user is the one who is going to use the application and they should be satisfied with it.
5. Take all possible support from your development teams.
When we work on team its not only about Testing when we are trying to deliver a best Quality product. We need to take all possible support from our development teams. When we find a bug, we need to follow up with the business and development teams that its being taken care off. When its a tight schedule for Testing, its a tight schedule for bug fixes as well. We need to provide as much data as we can to the development team. We need to do a through Root Cause Analysis (RCM) for the issue. Yes! Our job doesn't just end with finding a bug. We need to make sure that its fixed and the root cause is eliminated.
What I have mentioned above is my views and the way I handle such situations. I would request readers to share there opinion and experience on the same. And last but not the least, your feedback always matters to me. So feedback on any blog post is most welcome.
Until next blog post, Happy Testing!!!
Its good to be back after so many days!
Today I want to discuss something on a common problem in Testing world. Time v/s Test Coverage. I am sure every Tester comes across this situation in his career.
Its very obvious that a proper testing needs a proper time. But sometime the user needs the product earlier then even the user expected. What do we do on such cases? We can't handover a buggy application to the user!
In my Testing Life the following is what I have observed and have followed:
1. Test the application as much as possible.
You are a Tester. You don't let the application be buggy when it reaches Customer, even if you have less time. Give your best and test the application as much as possible. As a Tester we always believe that this application till have defects. Then this is the time to find as much as bug we can!
2. Exploratory Testing is your best bet in this situation.
Exploratory Testing is the way though which we don't test in a scheduled way. We test and we find. So when we have less time, we can prioritize our test and test the application by exploring. Do some random testing and check how application reacts to you.
3. Don't forget to cover the major functionality of the application.
When time is our concern, its the major functionality that we need to focus on. I have seen testers doing very good testing, but only to know that this functionality is not a major focus for this sprint. And the output is several major functionality for the sprint remained not properly tested. Hence its the major functionalities that we can focus on when we have to deliver in a tight schedule.
4. Discuss with the user about there usage preferences.
Its always the end user who is going to use the application. The best guide for you can be the business users or end users in such cases. Talk to them, understand what exactly they are expecting from the application from this remaining time? What they want to be tested on priority. Give your inputs to them on applications (what do you think might be the priority, how we can do a better testing in stipulated time). Remember that the business user or end user is the one who is going to use the application and they should be satisfied with it.
5. Take all possible support from your development teams.
When we work on team its not only about Testing when we are trying to deliver a best Quality product. We need to take all possible support from our development teams. When we find a bug, we need to follow up with the business and development teams that its being taken care off. When its a tight schedule for Testing, its a tight schedule for bug fixes as well. We need to provide as much data as we can to the development team. We need to do a through Root Cause Analysis (RCM) for the issue. Yes! Our job doesn't just end with finding a bug. We need to make sure that its fixed and the root cause is eliminated.
What I have mentioned above is my views and the way I handle such situations. I would request readers to share there opinion and experience on the same. And last but not the least, your feedback always matters to me. So feedback on any blog post is most welcome.
Until next blog post, Happy Testing!!!
No comments:
Post a Comment