Reviewers are essential to improving the quality and consistency of the material for this web site. They can provide objectivity and a fresh perspective on the material, and in turn they will be able to benefit from what they read. If you would like to be a reviewer we need you to understand the objectives of the review process, and what we need you to do.
You may have significant experience of one or more categories of non-functional testing. If so, you may be able to act as an initial reviewer for an author who is creating an example for one of those categories. Alternately you are welcome to review any published material using the feedback forms provided on various web pages, or to attend one of the regular review meetings, generally held once a month in central London.
Please read the author’s guidelines; available on the web site. This will help you to understand what the author is aiming to create. The aim of each example is to exemplify the use of a number of non-functional techniques within a single category. Your job is to help the author to deliver a clear, complete example that is consistent with the rest of the material on the site.
Check the material for:
|Grammar, clarity, and accuracy|
|Does the introduction provide sufficient information to help the reader to recognise the context of the domain example?|
|Are the requirements and specifications relevant to the test design? Note: they do not have to be too detailed, remember the focus is on demonstrating the techniques, not providing a detailed history of an entire project|
|Use of relevant non-functional techniques for this category of testing – ask yourself – would I use these techniques for a similar project?|
|Do the test cases conform to the techniques described in the Test Design section?|
|For the optional sections, is the content relevant?|
|Does the conclusion help the reader to understand how the test techniques have been applied to the domain being described in the example?|
Suggest changes tactfully, and if you are able to, consider providing some alternative choices. Please remember the author wants to describe some hard-won experience, and has probably worked very hard, to create the example.
22nd May 2003