I am a test analyst and I am happy about that.  But recently my new manager asked me to play a role as a test coordinator in a small project.  So I get to do some other things in addition to testing the software.  These other things include test planning, variance conference calls participation, test status reporting and making sure the test environment is ready.  The most challengeable thing I think is to make sure the test environment is ready.  Making sure the test environment is ready not just includes making sure the connection is working and the application is actually up, but also includes making sure the right code is there to test.  Since we have multiple projects going on and so many different test boxes to manage, sometimes the code drop is a little bit confusing and not that easy.  Where we should keep the old code (which is the same as the production code) and where we should put the new code in.  This small project we are working on, right after we started to test, we found out that the new code was not in that environment for us to test.  Good thing is that we realized the problem.  And once we raised this issue, people from other group sharing the same environment with us found out that their new code was not there either.  And so of course our developer had to do a new code build and put them into the right environment for us to test.  Confusing?  If you are a test coordinator, you might feel the same as me.  Please feel free to share some light.