A Small Story…
A boy and a girl were playing together. The boy had a collection of marbles. The girl had some sweets with her. The boy told the girl that he will give her all his marbles in exchange for her sweets. The girl agreed.
The boy kept the biggest and the most beautiful marble aside and gave the rest to the girl. The girl gave him all her sweets as she had promised.
That night, the girl slept peacefully. But the boy couldn't sleep as he kept wondering if the girl had hidden some sweets from him the way he had hidden his best marble.
Moral of the story: If you don't give your hundred percent in a relationship, you'll always keep doubting if the other person has given his/her hundred percent.. This is applicable for any relationship like love, employer-employee relationship etc., Give your hundred percent to everything you do and sleep peacefully.
I have put this on my blog because its the one which I follow in my life and will follow it throughout my life.Even when i am not interested to do some work while joining but once i am engaged with that one I will never leave leave without giving my 100%.Even people get shocked when I tell the fact of my disinterestedness towards that work.
Thursday, September 24, 2009
What should be done before switching from one project (P1) to another project (P2) in QA?
I had a similar experience,I left project when the project was in the middle phase.But till then I have completed with the test plan and test case specification and had much knowledge on the project.
Fortunately the project which I have joined was of the same type testing.
According to me,sharing some experience of mine,Don't know how other guys will be doing.
The responsibilities of project(P1):
1.Maximum try not to leave the project/or to contribute your time on the PI (if possible).
a.If this step you take should and must have proper time management.(If any one of the PI or P2 are bit small projects)
b.If the tester has much experience he can handle both.
(We can leave any project if we have a good one ahead,I agree but doing every project is a challenging only according to me. (its in my view))
2.Handover the tasks and give the status of the testing to the team leader.Its your responsibilty to do it.
3.handover the test cases specification and test reports.
4.In some companies it is mandatory that if a tester wants to switch he need to do knowledge transfer to someone(tester)who would be handling testing process.
The responsibilities of project (P2) :
1.First know the importance of your role and ofcourse the type of testing to be used.First know the importance of Project and then your importance.I agree this but if there is a testing team and you may be a member.You should know what is your importance as well.Without knowing we will not move to the project.
2.First step is to know type of testing and have minimum idea on the testing(it's good to have much knowledge).Type of testing means white box testing or black box testing.May be all testers may not have idea on both.
3.Need to have proper induction/knowledge transfer from the development team if project demands.
a.How to perform testing.
b.Clarifications of requirements of the project(Go through the Architecture documents).
c.Knowledge on the process to be taken in the project(bug tracking tool,repository,test environment and setup of it,knowledge on the tools,timelines/deadlines)
d.Should have minimum knowledge on the technologies used in the project
These are required for proper preparation of the required documents(SCM ,test plan and test cases specification)
and testing the project.
Fortunately the project which I have joined was of the same type testing.
According to me,sharing some experience of mine,Don't know how other guys will be doing.
The responsibilities of project(P1):
1.Maximum try not to leave the project/or to contribute your time on the PI (if possible).
a.If this step you take should and must have proper time management.(If any one of the PI or P2 are bit small projects)
b.If the tester has much experience he can handle both.
(We can leave any project if we have a good one ahead,I agree but doing every project is a challenging only according to me. (its in my view))
2.Handover the tasks and give the status of the testing to the team leader.Its your responsibilty to do it.
3.handover the test cases specification and test reports.
4.In some companies it is mandatory that if a tester wants to switch he need to do knowledge transfer to someone(tester)who would be handling testing process.
The responsibilities of project (P2) :
1.First know the importance of your role and ofcourse the type of testing to be used.First know the importance of Project and then your importance.I agree this but if there is a testing team and you may be a member.You should know what is your importance as well.Without knowing we will not move to the project.
2.First step is to know type of testing and have minimum idea on the testing(it's good to have much knowledge).Type of testing means white box testing or black box testing.May be all testers may not have idea on both.
3.Need to have proper induction/knowledge transfer from the development team if project demands.
a.How to perform testing.
b.Clarifications of requirements of the project(Go through the Architecture documents).
c.Knowledge on the process to be taken in the project(bug tracking tool,repository,test environment and setup of it,knowledge on the tools,timelines/deadlines)
d.Should have minimum knowledge on the technologies used in the project
These are required for proper preparation of the required documents(SCM ,test plan and test cases specification)
and testing the project.
Subscribe to:
Posts (Atom)