Best Practices for what?? You need to be a little more specific.
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
Best practices i can think about for any project are:
- as soon as you can, check requirements for ambiguity and un-testability. best case scenario one functional requirement should be one test case.
- review project documentation to filter out anything ambiguous (unclear references to other documents/paragraphs, adverbs, adjectives, poor examples, etc)
- test preparation (-> set up your scripts based on the requirements before you start testing)
- define environment owners, refresh environments and set up build schedules before the test phase starts. will give you some more time and more rest during your tests.
- defect tracking. even if considered as an administrative nuisance it will be a good tool for keeping an overview during a project and for key learnings after the project (which will lead to making it better in the next project).
- test documentation (-> document your test outcomes along with evidence. will facilitate communicating to DEV and be of help if you need to replicate something, or, to work on continuous systems improvement. i.e. some defect rated out of scope shouldn't be ignored on long term. your test scripts and evidence will help to keep it in mind and have easy follow-up later on)
Not having details, I hope that this will help...
Anyone: If I talk nonsense, please let me know. I'm working on continuous alexx improvement right now so feedback is highly appreciated.
Keeping track of all the requirements.
Having a DP analysis once in a month to chk with the various defects and discussing the various solutions with the team.
Providing the best trainings for the memebers.