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.
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.
2.First step is to know type of testing and have minimum idea on the testing(it's good to have much knowledge).
3.Need to have proper induction/knowledge transfer from the development team.
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.
My comments are intended to encourage you not to discourage you!
When you want to publish something on QT, you are most welcome and we require your help. QT has a feature called Blogs. I would advice you to publish blogs actively. Questioning and Answering by yourself is a old formula lets use the BLOGS technology.
Coming your Question and Answer. I believe your question shall be " WHAT SHALL BE DONE WHEN WE MIGRATE FROM 1 PROJECT TO THE OTHER"?? Are is it different?
My views w.r.t P1:
Maximum try not to leave the project/or to contribute your time on the PI (if possible) Why shouldn't we leave the project when we have a better, challenging and demanding project??
If the tester has much experience he can handle both. When we speak about switching from 1 project to other, where is the point of BOTH???
Your 2,3,4 are the Exit formalities w.r.t the project. Majority of the companies follow this criteria(KT).
My views w.r.t 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.
2.First step is to know type of testing and have minimum idea on the testing(it's good to have much knowledge). What do you mean by type of Testing? When you have worked on 1 project, still need have minimum idea about the testing???
3.Need to have proper induction/knowledge transfer from the development team. Do Testers learn from Developers???
I appreciate your enthusiasm in learning, take my comments positively and acquire more knowledge and info.
Thanks for your support.Please guide me if i am wrong in any sense.Thanks once again.
The answers for your questions are as follows.
-->Here after I will posting in my blogs if I want to publish.Thanks for your advice.
My views w.r.t P1:
1.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)
I do multitasking and in my company all do multitasking,I mean to say here a tester is a test engineer for 2 projects.
My views w.r.t P2:
1.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.Type of testing means white box testing or black box testing.May be all testers may not have idea on both.
3.Yes ofcourse,The tester should get the inputs from development team in case if the project demands.