Turbo Release Candidate Testing
Thank you very much for all your applications! I've sent a PM to everyone who is in the closer selection
Looking forward to working with you! The testing will probably start on Thursday.
Turbo Release-Candidate Testers Needed
We are on the final stretch to completing our work on the Engine Designer and the last new features, Forced Induction & Advanced Test Mode,
before moving on to the Car Designer.
For this final testing stage we will need some new blood in our testing team because we by now probably are too blind to see all flaws. So this is a
call for new beta tester candidates, but if you think we run the normal FAAAN (Fool-Around-And-Accomplish-Nothing) beta like most developers,
you are mistaken.
Release candidate testing will be done from the 28th of February till the 6th of March, and we expect anyone who joins to put in around 3h of
testing work during this time. This amounts to reaching 12 points in the testing system we are using, which is briefly described below. If you've
done well and would like to continue being on the testing team to be among the first to get your hands on a horribly broken and buggy version of
the Car Designer, you may choose to stay in for the upcoming subprojects!
The Testing System
We are working in a new system nicknamed POMMS (Project-Oriented Modular Motivational System) in which you are given "points" that add to your
"power level" for all the work you do for the team. Tested a scenario? Gives a point. Reported a bug? Gives a point. Completed a quest on the quest
board? Could give many points! While you are required to achieve a certain number of points to stay in the testing team, those that exceed
expectations will be rewarded accordingly (will get their place in the game credits and receive a special forum status).
During normal subprojects (i.e. not during RC testing), you are required to do (on average) about 1h of testing per week (4 points per week) during
at least a 8-16 week long period (one subproject). If your power level was one of the best among the testers during that round, your score is reset
and your name will make it into the game credits. Score carries over between subprojects if not reset, so someone who does solid work reaching
minimum score over several subprojects WILL make it into the reward ranks eventually. If you choose to join the testing team after this RC testing,
you will have all your points carried over to the next subproject.
So Here is the Deal
Requirements:
- You have preordered Automation.
- You are willing to follow the rather strict testing rule set and work on bug hunting and scenario balancing.
- You are willing to document your findings in a detailed fashion in the tools provided (Pivotal Tracker & Online Balancing Spreadsheets).
- You know that "testing" does not mean "just playing around" and is not fun all the time.
- You can and would spend ~3 or more hours on testing during the RC testing week.
Application:
- Write one post in this thread why you are interested in taking part in this.
- If we deem your application both reasonable and sincere, I'll PM you 2 short questions you'll need to answer.
- If your answers are satisfactory you will be accepted into the RC-testing and are welcome to join the testing team afterwards.
If you like the sound of this, you are most welcome to post down below! Also, be honest. We don't need people that just play around. Your help
would be greatly appreciated, and will make Automation a better product in the end - and the consequences of that should be to everyone's
advantage!
This invitation to join the testing team for RC-testing will remain open until the Monday the 25th of February. Post before then to be considered.
Cheers!
/Killrob