Blog

A tester among developers, or Alice in Wonderland, part 2

Sometimes, testers try to save their time and efforts by discussing defects directly rather than receiving detailed written reports. That said, as new developers and testers join the team, having clear descriptions is important to get them up to speed.
31 March 2015
Quality assurance
The article by a1qa
a1qa

If you missed the first part of the article read it here.

It would be unfair to ignore the risks that testers face working side by side with developers. For me, the description of the defects became the most serious risk.

Sometimes, testers try to save their time and efforts by discussing defects directly rather than receiving detailed written reports. That said, as new developers and testers join the team, having clear descriptions is important to get them up to speed.

Initially, I even tried to adjust the testing strategy depending on the specific functions of the developer. However, that was not correct, as sooner or later, it leaded to missed defects.

The first time I found myself in the epicenter of a developers meeting I felt like I was in another country.

But, as it always happens in the real life, after a while their language didn’t seem so foreign.

In the beginning I appeared at such meetings by chance (all meetings were held near my workplace), but it soon became clear that my presence at the general meetings was quite useful for the project.

Being a part of those meetings I understood every single detail and often was valuable in developing the testing strategy. Moreover, I informed team members how the code or its part would be tested, that helped to prevent defects proactively.

The abovementioned communication rules are pretty clear and simple. However, these obvious steps are rarely executed when the team is distributed across different floors, different cities and countries.

All too often, IT project participants forget that developers and testers have the same goal: to deliver high-quality software. No matter how talented its participants are, the project will never run smoothly if the team doesn’t strive for the same result. Providing a common goal helps establish a team environment and clear lines of communication. Everyone will benefit —software developers, testers, managers, customers, and the company in general.

The article by Anastasia Kotsevich — a QA Team Lead at a1qa —  was published on Stickyminds. Read the full article here.

More Posts

a1qa-articles
31 January 2023,
by a1qa
5 min read
Best of 2022 by executives: 8 most visited a1qa blog posts
Let’s look back and revisit the most visited a1qa articles of 2022!
Quality assurance
Test automation
qa-trends
12 January 2023,
by a1qa
4 min read
The future of software testing: top 4 impactful trends that will dominate in 2023
Consider the major industry trends for the upcoming year to know how to improve current QA strategies and stay ahead of the curve.
QA trends
Quality assurance
Test automation
test-automation
7 December 2022,
by Dileep Marway
3 min read
Release at pace with test automation: What, why, and how to measure success?
An automation-first approach is key to enhancing testing capabilities and increasing overall operational efficiency. However, I would suggest justifying its implementation, so that it can deliver the promised value.
Quality assurance
Test automation
what-is-a-culture-of-happiness
2 December 2022,
by Dileep Marway
3 min read
What is a сulture of happiness for a QA company?
Great culture drives employee engagement and satisfaction, contributes to an impressive work output, and improves organisational performance. But how do we build a culture of happiness? In this blog, I will share more on the answer to this.
Quality assurance
agile-qa
30 November 2022,
by Dileep Marway
3 min read
Agile QA – what is needed for greater flexibility and speed?
What should your QA team focus on to become truly agile, enable quality at speed, and contribute to lasting performance improvement? In addition to introducing test automation, I suggest considering shared responsibility for software soundness.
Agile
Quality assurance
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation
optimizing-budget-with-qa
31 October 2022,
by a1qa
4 min read
Optimizing telecom budgets with QA outsourcing: everything you need to know. Part 2 
Welcome to Part 2 of our blog on QA outsourcing and optimizing telecom budget with it. Let’s delve deeper into the topic!
QA trends
Quality assurance
optimizing-budget-with-qa
27 October 2022,
by a1qa
4 min read
Optimizing telecom budgets with QA outsourcing: everything you need to know. Part 1
Learn how to optimize telecom’s quality assurance expenses by relying on a trusted QA partner.
QA trends
Quality assurance
qa-trends-in-telecom
30 September 2022,
by a1qa
5 min read
4 telecom trends for 2023 and how to painlessly implement them with QA
It’s time to explore the telecom trends for the upcoming year. Let’s look at them together and also see the value that QA brings for their smooth deployment.
Cybersecurity testing
Migration testing
QA trends
Quality assurance
Test automation

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.