Code

What's Causing Testers' Dissatisfaction

What's Causing Testers' Dissatisfaction / Skillbox Media

Contents:

    Python Basics: A Free Course for Beginners and Experienced Programmers Four Impressive Projects for Your Portfolio Live Chat with a Teacher

    Learn More

    Margarita Trofimova

    Expert

    About the author

    Head of Quality Assurance at ITFB. I have been improving processes and products for over ten years. I believe my work makes a positive difference in the digital sphere. Vice President of the Russian Software Testing Qualifications Board, one of the organizers of the Moscow testers' club MSTC, and editor of the publication "Tester's Life".

    Links

    Currently, there is a trend towards sincerity and frank expression of emotions on the part of specialists and experts. Content like "What annoys a flight attendant" or "10 phrases that displease a designer" is actively appearing on YouTube and social media. Emotions also have a place in the IT sphere, and the ITFB quality assurance (QA) team decided to compile its own list of factors that irritate testers.

    It's incredibly frustrating when issues or defects appear in the bug tracking system without any description, limited to a title like "It doesn't work, please fix it!" It's especially frustrating to encounter such reports after real-world testing, when details such as steps to reproduce, data used, environment, and other critical aspects are missing. I won't even comment on logs, screenshots, or expected results.

    It's also frustrating when a developer submits code for testing without even performing basic checks. For example, the "Close" button doesn't perform its intended function and instead generates numerous errors, causing the system to freeze. Although the developer reports that the issue has been passed to QA, the core functionality is inoperable. As a result, you have to waste time realizing that all your efforts were in vain.

    Sometimes, teams that worked on the same issue previously don't create documentation. As a result, you're faced with functionality that works completely incomprehensibly. In such a situation, it's difficult to determine what exactly is a bug and what is intended as part of the functionality. Furthermore, the lack of documentation is irritating, making it impossible to ask for help or finding the information you need difficult.

    Slow and unresponsive rigs are annoying, especially when they're not yours and you're powerless to fix them. And the test environment requirements you sent out aren't even something customers and other teams bother to read and have no intention of reviewing.

    It's frustrating when you have to persuade a programmer to do their job.

    — It doesn't work here.

    — It's not mine!

    — You wrote Dev Result!

    — Oh, well...

    There are cases when a new build has just been submitted for testing, and defects immediately appear, and the manager is already wondering when it can be launched into production. This is irritating: how can I know how long it will take a developer to fix these bugs? My competence is limited only to testing issues.

    It is irritating when new tasks are added in addition to those already planned. Especially if this happens without the participation of a tester. The manager passed the task to an analyst, the analyst performed the analysis and passed the information to the developer, and then suddenly you receive all these changes. And no one explains who, what, how and where this task came from.

    In a situation where there is a lack of unity in the team, the employee is aware of the problem, but it does not directly affect him. As a result, they take no action to provide assistance or support.

    It's annoying when a project doesn't have a versioning system—it leads to a situation where it's unclear which build you're currently testing. As a result, it's impossible to indicate the build number where the defect was discovered in a bug report.

    When a developer sets up the logging system so that the resulting records resemble machine code that still needs to be interpreted, this can be a real challenge, especially under limited testing time.

    It's annoying when a client can't clearly communicate their product requirements. Here's a typical situation:

    Client: Everything is fine, but could you clarify why the combo boxes indicate exactly these values: first, second, third?

    You approved this command yourself.

    Client. Hello? Let's change it to one, two, three...

    The next day:

    Customer. I believe there were other options in the combo boxes, right?

    Team. Yes, but you approved the current ones.

    Customer. Oh, right... Okay, then let's use first, second, third...

    — Something isn't working here.

    — That's not mine!

    — You wrote Dev Result!

    — Oh, okay...

    Customer. Everything is fine, but I'd like to understand why the combo boxes show these names: first, second, third?

    The team was approved by you.

    Customer. Yes? Let's change it to one, two, three...

    The next day:

    Customer: I think there were other options in the combo boxes, right?

    Team: Right, but you approved the current ones.

    Customer: Ah, right... Okay, then let's use the first, second, third...