This afternoon I have been going through roadtest applications. I do this on Fridays because it's quieter and I am left alone to really read and absorb what has been written in the application. The following came to my mind while reading them regarding why some applicants don't get selected as official roadtesters:
1. If you a provide a test procedure on a MS Word doc that is eleven words long. Test procedures tell a lot about an applicant's skills, knowledge, abilities, etc. Most of what we roadtest has a level of complexity that requires more than 11 words to describe what a roadtester will do in a competitive fashion.
2. If you provide a test procedure that is an academic research paper that's someone else's work without an explanation, commentary or personalization to your ideas for the roadtest. Of course, you are welcome to use a research paper as a reference to your own self-written test procedure. But the test procedure itself has to be your own work and explain to the best of your knowledge what you are going to do. You don't have to write a book, but 2 to 3 paragraphs is an amount that can tell me where you are going to go with the roadtest.
3. If you provide a test procedure that is a resume where the skills, experience and credentials are not relevant to the product being tested without a commentary or explanation. (For example, you could have a degree in chemical engineering and tell me you have done a lot of work with the Raspberry Pi, then that is fine.)
4. If you provide a test procedure which is an amusing image (jpg, png, etc) and nothing else. Perhaps I lack the sense of humor to understand why I am receiving an amusing image for a roadtest on sensors. Are sensors inherently amusing?
5. If you provide a test procedure that looks like a generic testing and performance procedure from a university textbook and is not adapted to the product being roadtested, using your own words.
