Yes , I have been doing this for many years now with no realization as to what is being going on, But I was involved in all types of testing ....... ,
With so many activities as a Tester,Test lead or what ever as long as you have Test appended to your role you do so many important activities but nothing is captured or documented on your profile .. reason is you are not capturing smallest to the biggest and over the period you loose them ,if not refreshed timely. So keep some time for this on a week end or a off day were you feel i need this at the back of my head and refresh it ..and not at the time of a interview :) or if any org you have to certify for.
You need to intrigue yourself and find a way to find your testing knowledge health if its red or green or dead :) , unlike other technologies we do not have a text book or MSDN to tell you this is all i know and if this is all its not ... We/I have tested so many products for customer x, y , ....Z each product or project is unique were you are placed in different position each time , i mean when you have all day to test and rest some time in slog overs you need to win the cup by scoring high its indeed a stressed up and down situation,But we do it and shoot the developers with some defects ..some may be missiles..I am pointing it out to say that our learning curve is parabolic we start with so much of knowledge and it dies down and goes up on the other side were we learn new tools,techniques and so on.
What I know in Testing is directly proportional to what I know by Testing .here one is activity and other is a topic.let me not confuse you more, An activity is the process of understood topic.always we forget the topic as we progress with our activity.
Why I say its testing is you need to know of it by the book value than , saying i have done it but just some time back were i cannot get it now....its dangerous..so keep in mind conceptual know hows .....of any topic you come across....while doing Testing.
With so many activities as a Tester,Test lead or what ever as long as you have Test appended to your role you do so many important activities but nothing is captured or documented on your profile .. reason is you are not capturing smallest to the biggest and over the period you loose them ,if not refreshed timely. So keep some time for this on a week end or a off day were you feel i need this at the back of my head and refresh it ..and not at the time of a interview :) or if any org you have to certify for.
You need to intrigue yourself and find a way to find your testing knowledge health if its red or green or dead :) , unlike other technologies we do not have a text book or MSDN to tell you this is all i know and if this is all its not ... We/I have tested so many products for customer x, y , ....Z each product or project is unique were you are placed in different position each time , i mean when you have all day to test and rest some time in slog overs you need to win the cup by scoring high its indeed a stressed up and down situation,But we do it and shoot the developers with some defects ..some may be missiles..I am pointing it out to say that our learning curve is parabolic we start with so much of knowledge and it dies down and goes up on the other side were we learn new tools,techniques and so on.
What I know in Testing is directly proportional to what I know by Testing .here one is activity and other is a topic.let me not confuse you more, An activity is the process of understood topic.always we forget the topic as we progress with our activity.
Why I say its testing is you need to know of it by the book value than , saying i have done it but just some time back were i cannot get it now....its dangerous..so keep in mind conceptual know hows .....of any topic you come across....while doing Testing.
No comments:
Post a Comment