Lately I’ve wanted to tag some stories with “testing” (e.g., Testing Distributed Systems), where the primary focus is on the testing part, not the creation/coding part. I know that tag proliferation is an issue, but this seems like a fairly large hole, unless I’ve missed something.
I would like this, too. I’ve been thinking about testing a lot lately.
Though to me it’s blurirng into formal verification like types, refinement types, and proofs. I don’t know if something like “high assurance” or “engineering” or “reliability” is the right word, let alone precise enough to be useful as a tag.
I think this should be part of the “programming” tag, as testing should be part of programming. But that might be too narrow.
That’s how I’ve been labeling it, but they’re not the same. Testing a system at scale, say, is quite different from developing/coding such a system. Testing != automated tests written in code.
I think it should be subsumed by the
programminglabel because testing is a requirement of prgoramming, at least currently. I think we should be promoting such a culture rather than there being programming and that other thing called testing. But I understand what you’re saying, I am just on the side that there are already too many tags so trying to find ways to keep them less.