As per existing project( but beware not tell them you only worked on existing project) whenever new functionality or new module added to project we are doing the following things.
1. When we got a mock (Requirements documents from clients).
2. Firstly go thoroughly of docs and writing test cases.
3. Executing test cases who created behalf of Clients requirements.
4. If found a bug, logging that bugs in bug tracking tools like(Jira, Ticketbuilder,Quality Center).
5. When bug get fixed, again verifying that bug etc.
6. Whenever new build enforces, doing smoke testing for quick test of some major functionality after that doing regression testing of whole sites.
7. On daily basis whatever the work done by the team, reporting to clients.
8. Assisting to newbie( new member) to get familiar with projects.
9. Providing technical support to team member to setup environment to carryout testing. etc.
10. Carryout chatting, with off-shore QA member to exchange latest information regarding projects.
10. Carryout chatting, with off-shore QA member to exchange latest information regarding projects.
Important: You must remember how to log a bug in bug tracking tools like following
1. A bug have ( Title,Summary or Heading)
2. Priority( Critical, High, Medium, Low)
3. Severity (Show Stopper, High, Medium, Low)
3. Status( Open, Alpha & Beta verified,Inquiry, Build hold, Re-assigned, Assigned,Close, In progress etc)
4. Ticket type( Bug, Re-work, Release, Maintenance, New functionality, Support)
5. Steps to reproduce.
6. Environment( in my case qa2www.... or on production)
7. Os/ Brow( XP/Vista, win 7, Mac: IE7, 8, FF 3.6, Safari etc)
8. Assignee( either assign to developer or senior QA member for review)
9. Description( here u write, what u actually seeing in bug)
10. Comments( Generally but by qa member and developer)
11. File attachments( screenshot, video file) for bug proof.
