Writing Tests in Plain English: A Short Style Guide for Codeless Testing
There is a common assumption that once a tool lets you write tests in plain language, the hard part is over. Type what you want, get a test, move on. In practice, the quality of a plain-language test depends heavily on how it is written. A vague sentence produces a vague test, and a vague test either misses bugs or fails for reasons nobody can explain. Writing good test descriptions is a skill, and it is one that product managers, designers, support staff and business analysts can learn quickly.