Pop quiz…. here is an article I recent stumbled upon, which side (pro or con) do you think the author takes?
Pros and Cons of Requirements-Based Software Testing
For something that is essential, fairly fundamental and seemingly straightforward, requirements-based software testing sure does generate a lot of discussion. Rather than representing opposite extremes of the same continuum, pro and con camps come at the topic from disparate perspectives. Advocates of requirements-based testing tend to be analytical, whereas opponents tend to couch their objections in more emotional terms. Each approach has its own strengths and issues.
Turns out, those emotional folks are the proponents of agile, or at least the author’s faulty understanding of agile.
A key requirements-based testing issue is that some prominent voices within the testing community deride it, often loudly and with great emotion. They say that the rapid pace of constantly changing business and technology makes it essentially impossible to define requirements ;therefore trying to test based on defined requirements is a waste of time. They say instead of spending time trying to define the requirements, just go code and run tests.
He never uses the word “agile”, but does go on to tip his hand:
Second, foes of requirements-based testing often speak monolithically as though the only alternative to their favored just-go-code-and-test approach is interminable analysis paralysis in a mindless and inflexible exaggerated "waterfall"…
The actual topic here (requirements-based software testing) is not important. What is interesting the author’s lack of maturity. A simple change to the title to indicate this is not a balanced pro/con piece would help, but mischaracterizing and belittling the opposing view is always bad form.