Easy way to fail testing

Sometimes testing does not bring the desired result. That is, the work is boiling, features are checked, bugs are repaired, even some statistics are collected, but after the release it turns out that the product is stuffed with defects, like sunflower seeds, - and users, characteristically, spit.
Who is guilty? Of course, everyone is guilty - both managers, programmers, and analysts, but let them learn their own lessons.
Well, testers.
Also.
To blame.
Yes?
Yes. And the point is often not technical problems, but quite human ones. No, it happens, of course, that the uprising of machines breaks all the plans, or that the plans were initially unfeasible. But even in a non-force majeure situation, the tester has enough ways to fail testing by working hard.

That's not mine

This is developed in the Samara office, let them deal with their defects themselves. Not eyeless after all.
This is what Kolya was given to test, which I will climb. Let him study.
Three more iterations back gave this feature. Probably that is how it should work.

Such an approach is not necessarily due to indifference. Maybe a person is sincerely sure that the Samara office will successfully find and fix everything; and Kohl - and so nervous when he advised something. Yes, and their tasks so much that freshly made coffee remains unabsorbed. Not so in general. Although it was enough just to ask “hey, why is it like this?” In Samara or Kolya.

The developer said it was intended

And I believed it.
And I did not think that could be otherwise.
And we have no analysts; as the programmer said, so it’s right.
And the analyst is on vacation.
I even wanted to double-check, but I forgot - so many tasks ...
')
Here, of course, as with a dinosaur, - either a meeting or not. In the sense - either the developer rights, or not. Again, you can run into both stupidity / naivety, and from sincere respect, if the authority of this particular developer is high. The only working option - check without looking at the person. Everyone is mistaken.

It did not work, but suddenly it worked - apparently everything is in order.

I just asked the developer, he did something, and he works.
I just changed those fifteen parameters at random.
For old objects, however, it does not work, but for new ones everything is in order.
Oh, and I, on the contrary, with the new something strange. But the old is OK!
Yes, just drank tea, and everything was fine. Who knows what was there.

Are you a tester or someone? Leaving the problem, not fully understanding what's the matter, not understanding the programmer's explanation, well, why are you so?

For developers, the problem does not repeat

He has a newer library there - he will get into the next build. All is well, in short.
Apparently I have something wrong with the settings, well, those fifteen that I changed - remember?
Yes, we have iron is just frail, that's all.
Well, I saw it myself, it works for them!

Damn it!

Oh well, still such nonsense to report

We already have a lot of bugs.
And such a trifle, no one will notice.
Yes, and get to this screen, two of the hundreds.
Point, comma - what's the difference?
By the way, the bus is about to leave.

There can be anything. If this kind of defects and so on - half a bugtracker, and everyone is stuck in a state of "sometime not now" - yes, you can not start it. And so I would be reinsured. Well, at least I would ask who, yes?

Why would he not work on another database engine, another OS?

SQL it is SQL, what's the difference?
So what if that one is 64-bit?
Well, here's another update to type on the machine ...
Checked already works.

Get out of the profession.

It was not clear, but the developer explained

Here in the interface they asked something, did not understand what it was about. But Cyril explained how. It turned out to be easy.

Well, yes, and that before explaining for three hours I could not figure it out - this is a trifle. We will not add tips to the product or explain in the documentation. Why, if you now understand everything?

Feature? I checked, the button works, everything is fine

Usage scenario? No, have not heard.

And so - the work is in full swing, all in business.
All is well, in general.