Description
Especially with regard to Pester as we rely on it as our test infrastructure, but sometimes Pester does not have a feature which we would like. Should we code up our own solution and use it?
I am very concerned about this because it does not help the Pester community and places a burden on anyone who wishes to use our solution to get one more module, or script. Specifically, when checking for error conditions, we would rather validate against FullyQualifiedErrorId rather than the message (which is what Pester provides). I would be happier to have a PR filed on Pester which implements an assertion for something like ThrowFullyQualifiedErrorId (or similar) rather than coding around this in our own code. This allows Pester to have something generally useful and avoid more and more unneeded custom code.