This is a tongue-in-cheek reference to Test-Driven Development (TDD). TDD is a software development strategy largely revolving around using development tests to drive implementation towards fulfilling the requirements.
Tester-Driven Development, however, is where the requirements are the shortcut and it becomes the case that the software team starts specifying the requirements through bug reports. Tester-Driven Development can also be referred to as Bug-Driven Development as it essentially results in bug reports being used to specify actions and features that developers should implement.
For example, a developer builds a tool to export data from a database to a spreadsheet. It works perfectly, but a tester still comes back and raises a ticket saying that there is a bug in the product; they say that it doesn't contain the ability to export to PDF. If this wasn't in the requirements it shouldn't be raised as a bug. And yes, you should have requirements.
QA teams and...