Don’t look for bugs but try to explore the application and play with it. Goal is not to find maximum number of defects but to improve user experience for users who are going to use the product. Aim is not to impress your manager by locking maximum number of bugs but to bring joy to customers who are going to use the application.
No day-dreaming while attending requirements discussion. Keep asking questions and remove all ambiguous requirements. Documentation is important. Helps you keep track of things.
Prepare User Stories from the requirements. Write Test-Cases for the features. Map User Stories to Test-Cases. This helps in covering all bases. Club Test-Cases in different categories like Sunny Day Scenarios, High Impact Area, Corner Cases etc.
Keep the stakeholders i.e. Manager informed and share the status. Have regular conversation with Product Manager to know what are the critical flows in his/her eyes. Have friendly relationship with your development team. During conversations you get an insight into what are the weak areas and which feature or functionality need extra attention.
Stick to the agreed plan. Execute Test-Cases in systematic manner. Update Test-Cases if required while testing. Log defects properly with all necessary details to avoid delay and confusion. Prioritize your responsibilities and keep track of everything.
Work in collaboration with team members. Bring in the knowledge gained while testing some other product or while using an existing application. Improve User Experience of your product by looking into similar products. After testing is complete and application goes live, keep an eye on customer feedback.