Hello All,
Yesterday I attended one session for Weekend Testing which inspire me to start blogging as I want to share the learning that I got from it.
The session was about making a plan or strategy of one application. Here is the link of application: Taskcoach. As per the developer's requirement, entire testing needs to be completed in 3 hours. If you look at the application, no tester can say the he/she can able to complete the application testing in 3 hours.
The mission of session is to prepare some sort of Test Plan or Test Strategy document that describer how to complete the testing in 3 hours. The interesting portion is each person has to pair up with other person to prepare the document.
I had pair up with one person who is currently tester at Japan ( I don't know his company or any other information). He has 7+ years of exp. in testing. Hence I thought it would be good for me as I just completed 3 years in this field. What we both thought was to made one checklist that describes the points which needs to be tested in 3 hours. We both divided the toolbars and started to gather points. The plan seems to be worked fine as at end of hour we collected almost 15-16 points to test.
After an hour, we started to discuss with all other persons (there were total 8 persons who joined the session), on how we progresses the stuff and we were asking questions to each other on doubts. In discussion, one interesting question raised that "what exactly developer wants to test in 3 hours?". Frankly speaking, even this question was not came into my mind also although during my daily job, I am regularly asking same question to developers.
So the point here is sometimes, we are just assuming that whatever application/system given to us (testers) are the final one and we just started to plan and test the application. We even don't bother to ask to manager or developer what exactly they wants us to test. And than the problems and confusions starts to occur as tester required more time to complete and manager are as usual always in hurry. In above session, actually developer only wants to test whether the application is working as per MS standards or not. And whatever list or plan docs that we all guys had prepared, no doc reflecting the main point. At one moment, I got laugh on myself too.
The thing here that I want to highlight is before doing any planing or deciding any scope, better to do a meeting with manager/developer. It will save your time and will give you better insight of what exactly needs to be tested, instead of going for entire system testing. This case is really helpful for those testers who are working for the Product based companies. As these companies always wants work on enhancements in existing product.
The other thing that I learn from session is how to work with some unknown person. In our testing life, we always be in situation where we have to dealt with very new person: If you are manager than you have to deal with new resource under you and if you are normal tester than you have to deal with new persons from senior management. From this type of exercises, you can easily starts communicates and build up relation with new person. In my example, I had to deal with a person who is far more experience than me (from 3 to 7 years).
At the end, I knew that this is my first blog and it might be chance that many of you or even none of you likes this post. But any reply if I will get than you are really welcome. As I believe that you can only learn new things by sharing your knowledge.
Any comments good or bad, most welcome. :)
Yesterday I attended one session for Weekend Testing which inspire me to start blogging as I want to share the learning that I got from it.
The session was about making a plan or strategy of one application. Here is the link of application: Taskcoach. As per the developer's requirement, entire testing needs to be completed in 3 hours. If you look at the application, no tester can say the he/she can able to complete the application testing in 3 hours.
The mission of session is to prepare some sort of Test Plan or Test Strategy document that describer how to complete the testing in 3 hours. The interesting portion is each person has to pair up with other person to prepare the document.
I had pair up with one person who is currently tester at Japan ( I don't know his company or any other information). He has 7+ years of exp. in testing. Hence I thought it would be good for me as I just completed 3 years in this field. What we both thought was to made one checklist that describes the points which needs to be tested in 3 hours. We both divided the toolbars and started to gather points. The plan seems to be worked fine as at end of hour we collected almost 15-16 points to test.
After an hour, we started to discuss with all other persons (there were total 8 persons who joined the session), on how we progresses the stuff and we were asking questions to each other on doubts. In discussion, one interesting question raised that "what exactly developer wants to test in 3 hours?". Frankly speaking, even this question was not came into my mind also although during my daily job, I am regularly asking same question to developers.
So the point here is sometimes, we are just assuming that whatever application/system given to us (testers) are the final one and we just started to plan and test the application. We even don't bother to ask to manager or developer what exactly they wants us to test. And than the problems and confusions starts to occur as tester required more time to complete and manager are as usual always in hurry. In above session, actually developer only wants to test whether the application is working as per MS standards or not. And whatever list or plan docs that we all guys had prepared, no doc reflecting the main point. At one moment, I got laugh on myself too.
The thing here that I want to highlight is before doing any planing or deciding any scope, better to do a meeting with manager/developer. It will save your time and will give you better insight of what exactly needs to be tested, instead of going for entire system testing. This case is really helpful for those testers who are working for the Product based companies. As these companies always wants work on enhancements in existing product.
The other thing that I learn from session is how to work with some unknown person. In our testing life, we always be in situation where we have to dealt with very new person: If you are manager than you have to deal with new resource under you and if you are normal tester than you have to deal with new persons from senior management. From this type of exercises, you can easily starts communicates and build up relation with new person. In my example, I had to deal with a person who is far more experience than me (from 3 to 7 years).
At the end, I knew that this is my first blog and it might be chance that many of you or even none of you likes this post. But any reply if I will get than you are really welcome. As I believe that you can only learn new things by sharing your knowledge.
Any comments good or bad, most welcome. :)
