I have been working in testing for more than 9 years, and now I'm a Senior Test Engineer in a large IT company. Active participation in conferences and company projects allows me to interact with other testers, see their successes, problems and solutions. As my experience grew, I began to fall into various mental traps, but I learned to spot them after a while. These traps make you act in a patterned way, hang anchors and set yourself up for the same outcome despite different inputs in similar situations. This leads to a shrinking radius of vision until it becomes zero, so we have a point of view on which we blindly stand, which in turn ends up missing bugs and losing product quality.

In my talk, I will consider the traps I have fallen into myself or noticed in others, and I will share techniques that help me sidestep dangerous judgements and look more broadly at issue at hand. 

I have been working as a Senior Test Engineer in a large IT company for 4 years and have been participating in the different professional conferences actively. During this time I've heard thousands of stories from the QA-engineers about the tasks that need to be realized "still yesterday." The final of these stories can be different: the quality of code become worse because of rush, the time of the project realization prolongs, relations with customers deteriorate and testers accumulate professional stress.

What need a tester to do to be prepared to sudden problems at any given time?

In my report I would like to tell you how can classify urgent tasks. Also I will share techniques that help me and my colleagues to accelerate the testing process improving the quality of the produced functional.

Welcome it will be very useful for you.