this post was submitted on 09 Aug 2024
1328 points (98.1% liked)
Programmer Humor
19563 readers
1111 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That sounds strange. I cannot comment on your particular case without seeing the test artifacts.
Generally speaking, there is nothing wrong with tests that ensure bad input doesn't break the system, as this can easily lead to incorrect system states, damage to the environment, loss of data, money, reputation, and even lives - although most systems are not critical enough to threaten lives.
You wouldn't need QAs if you only needed to validate that the product meets the requirements. In a typical company, many people are involved in that process. This includes the developer who wrote the code, the developer who reviewed it, and the people who conduct acceptance testing, among others. If your developers produce code that doesn't meet the requirements, you're in trouble.
I'm not saying that QA shouldn't validate whether the system meets the requirements, but you don't want them to do just that.
If they didn't properly test validation I would complain about that, what that regularly miss is a test showing correct function for each major use case
So it sounds like you need to use the words to tell them, do you know testing types and strategies so you can tell them which to employ?