The "Examples are Always Handy" section is confusing. It would be better if we used prose (rather than just bullet points) to indicate clear thought, used wikified external links to avoid cluttering the page with URLs, and helped the user understand the examples. This section should demonstrate, in a visible way, how a person thought through a specific question or idea, wrote the English description, and then wrote the computerized test. If we want to do that three times, once each for a configuration, a browser-specific issue, and a global problem, that's fine. Also, if we mention specific colleagues, we should explain why we are doing that (an indication that the test-writer's work is useful? general shout-out?).
Topic on Talk:Quality Assurance/Examples
My main problem was to have this text as a section of QA/Browser testing/Search features so I have moved it to an own page. We have enough pages explaining many aspects of browser testing, they are potentially useful in any event and we should keep working on improving them. The weekly goal pages need to be short and go to the point, linking to other pages as needed.