Beta Testers are expected to report back any unusual behaviors, glitches, errors, FAHlog messages, performance issues, etc. in the Beta Forum. A true Beta Tester actually tries to break the software
(but not violate the EULA), use it in many scenarios, system configurations, and tries all combinations of settings, switches, clients, etc. They then have to try and figure out exactly what they did to break it, and report their findings in a detailed manner. Thus providing detailed feedback is very important during Beta Testing. Moreover, Beta Testers must have a fairly good understanding of computers and their inner workings so they know how to fix something when/if it breaks during Beta Testing. They accept the risk of running into an occasional problem, and will be tolerant of those problems. By posting your request to join, you have indicated that you have accepted these conditions of membership. (In your request, please state that you understand and accept them.) This is a brief overview but can learn more as you read the posts in the Beta Forum starting with
Beta Team - Rules Of Engagement, provided you have been accepted.
Note: A quick recap of what Beta Testers do:
A) They test work units from new Beta Projects
B) They test new beta versions of FahCores
They don't test new F@h Clients. That is handled separately and generally done as an Open Public Beta: Forum