Just found out about this article which has some advice for becoming a beta tester along with the bugs, beauty and benefits of beta testing, it’s quite an interesting read.

here’s an extract of the last paragraph:

Advice for beta testers
Beta tests are not something to enter into lightly. You may need to put lower priority projects on hold or delay other projects by a few days or even weeks. It’s a strain because you still have to get the other work out, so you’re working lunches and overtime, Barton says. So, if the beta test is low-reward or other high-visibility projects are going on, or you don’t have a test environment prepared, don’t do it, says Barton.

Negotiate everything upfront
If you want the names of support people or other terms of agreement, make sure you do it upfront and in writing. You can’t just pretend your previous agreements don’t exist anymore, Barton says. It has to be done legally and in an organised manner. And, while financial incentives can be issued, be sure you get a commitment before you go into testing, when you still have leverage, he says.

Apply yourself
When you’re applying to be a beta tester, fill out the form completely, says Michael Fine, director of client services for Centre Code. We get forms where they don’t give data on what equipment they have to test with, he says. And people who can’t spell are less inclined to be chosen. Abide by the confidentiality rules, he says, and don’t expect a miracle. Don’t set overly high expectations for the product before you get it, he says. This is beta; it’s being tested. Go in with an open mind.

Via: Software Testing London UK