If I could add some experience of what I have seen to be the KEY FAILINGS of PREVIOUS BETAS (17, 18, 19)
To all the participants
The quality of your feedback is important - if I look at a sample of bug reports posted in the TA forum currently, it is very NOISY!
It will not win you favour by trying to find the most bugs. It is not a competition and there is no prize.
It helps if you complete the bug template, every time on a new bug, and you state what you have tried to prove it is a bug and not just a kink in your setup. Replication is important.
It helps if you can confirm and add evidence to exisiting bug reports. You can even disprove them, or say how you found a solution.
It helps if you do not jump in and out of Multiplayer lobbies looking to race elsewhere or when you crash out. Spectate and rejoin the session at the next race. Stay connected.
We do not need endless posts about people's thoughts about the game. It is a BETA. You will be asked your opinion so save it, and take the opportunity at the end of each focus period (usually a week). Far more chance of it getting read then, than lost in hundreds of (hopefully) quality bug reports.
Look for similar bug reports and add to them. Find and confirm bugs in your current game are fixed!
To the moderators (keep reading participants)
Sorting the wheat from the chaff - merging threads and deleting (or dumping posts) is key to retaining focus. I hope you have some kind of standard message to send to a user informing them that their post has been removed due to being incomplete, not contributing or spam.
Consider removing those from the program that have difficulty signing up. It is no good having people who cannot communicate what they have found or are not technically minded enough to do the simplest things like sorting out emails and usernames.
In the end
To be a beta tester you should be able to produce diagnostic information;
the Report Code
a dxdiag, a crash dump, hardware settings file
the ability to take and share screen dumps, post video to email or share privately (not unlisted) on YouTube (visible to only yourself and the Codemasters beta e-mail address)
a detailed description of how to recreate the issue
DO NOT sign up if you just want early access to the game - you will be disappointed, the game is not usually made fully open, you will get specific modes and be asked to use them for a period of time. If you can find and quantify ONE bug during this period it will be helpful. If you can confirm TWO others, that's great.
It will not be open all the time, you may have periods where you are locked out. PS4 users have previously snoozed the game to get around this. Don't bother posting errors, they don't count because the condition is not normal. It has been general that you have been granted access to play according to the time you log in. Codemasters, I suggest if you can somehow log people out of sessions automatically once an hour has passed beyond the sign-in cut off that would be good.
Mails have been sent and access granted. I'd like to take this time to thank everyone for applying. We've had record applicants this year, and it's not a easy decision for users.
What I can give away is a little information for consideration next year. A great way to ensure you are considered well for the BETA, in my opinion (which matters all of a sudden) is:
Posting complete bug reports in the game cycle. This is the decider for me. If you post reports and test correctly while a game is live, we'll want you 😛
Correct forum behaviour and etiquette. Be active and contribute to a forum that is a great place to be. Be constructive, critical and respectful to others.
If you have a problem or an issue, think about how the information we need to fix it. Just because it's not BETA season, it doesn't mean we are not looking to improve the game.