Thread:Talk:QA/Browser testing/How to contribute/improving the volunteers' experience - bz queries/reply

I also learned a lot with my first exercise of writing scenarios, not only about the exercise itself but also about how to improve our documentation.

The two main lessons for newbies I got, that are not explained:


 * Focus on explaining the bed-time story. Don't get obsessed with the right syntax. More experienced writers can and will polish your syntax quickly (and you will learn from their fixes) but they will have a hard time if thew story is not clear.
 * When in doubt between writing a scenario too generic or too detailed, go for too detailed. If needed, someone can and will come after you and abstract the details into regular expressions. The the way around doesn't work, and a too generic scenario might have to be investigated from scratch.

About listing bugs: YES! In the past weeks, and during the event, I asked for real pointers to real tasks. I don't believe in newcomers "finding a feature they like" or "looking at the backlog for the kind of things to do". And even for more advanced scenario writers: we can't expect them to check what scenarios exist and therefore what are welcome. A Bugzilla keyword for reports welcoming an automated test?