Its pretty easy (for Andriod at least):
- When theres something to test you will get an email with the download link.
- You download the .apk file and install it (you need to allow 'Unknown sources' under Applications so you can install it)
- Run it, drive with it, play with the settings and features, generally try and break it. Driving normally with it can also find bugs. Be prepared for it to crash or even restart the phone.
- Any bugs/problems you find get reported into a thread here, and the Waze team will keep track of the bugs and/or reply. In some cases you may also need to use the 'Send logs' feature and provide the date and time so they can diagnose what the issue was.
- Fill in the link to the survey in the email so you can indicate how you feel its working.
One thing that does annoy me is that reporting a bug has to be redone on every new Beta release, theres no real changelog or bug register beyond the fourm. So it may require you to try a lot of times and never know if it has been worked on - Really something the devs need to provide is access to their internal bug register so we can see if it needs to be retested or if we should focus on other bugs.
Tip: when a beta comes out it normally doesnt start in debug mode, navigating to 2##2 enables debug mode and 'Send logs' will include much more information than the normal version.
Was that what you were after?
Samsung Galaxy Ace (GT-S5830) - Gingerbread (Andriod 2.3.5)
New Zealand - Waze Client Beta Tester