#ProgrammerTesting

Maaret Pyhäjärvimaaretp@mas.to
2023-09-21

A tale of three testers but entirely different frames of reference. #ContemporaryExploratoryTesting and we knew coverage, found bugs and hit schedules. #DomainSpecialistTesting and we covered only requirements, insufficient testing, fuzzy communication on status. #ProgrammerTesting got road blocked to fixing, leaving coverage low and missing bugs.

J. B. Rainsberger (he)jbrains
2023-02-21

I haven't read this post yet, but I expect you'd find it helpful even if you didn't entirely agree. It regards problems in naming tests and proposes a superior system.

I invite you to consider their system in order to learn from it, even if you don't adopt it.

I have found it enough to give myself the freedom to simply remove duplication from within the names of tests. That encourages reorganizing them in ways that tend to avoid these problems.

mstdn.social/@mkutz/1099021846

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst