In the dynamic world of software development, Quality Assurance (QA) testers play a vital role, because they make sure that every feature and function works as intended and products meet the highest standards before reaching users. At platformOS, both manual and automation QA testers contribute to delivering reliable, high-quality software. In this article, we provide an inside look into the daily routines, tools, collaboration methods, and personal insights of manual QA testers, based on interviews with Alexa and Dóra (manual testers) and Filip, Rafal and Damian (automation testers). 

Daily Professional Routine

Manual Testing Perspective

When asked about their daily workflow, Alexa and Dóra shared that their mornings typically begin with a check-in. Then they review the QA lists on Trello or GitHub Project boards, depending on the task management platform used for the project). After that, they prioritize tasks, and align on what needs to be accomplished. This includes testing issues from project boards, addressing messages on Slack, and participating in daily meetings with product managers (PMs) and developers.

“We log in, check the QA lists, and discuss our plans for the day. After prioritizing tasks, we dive into our work,” they shared.

Their tasks usually arrive in the form of tickets, which land in the QA lists and outline what needs to be tested. These tasks may involve: 

• Testing new major or minor features

• Checking modifications to existing features 

• Reviewing UX/UI changes (such as text updates, link changes, or design tweaks)

• Retesting bug fixes to ensure proper functionality

Occasionally,  they receive tasks outside of the project boards,such as direct assignments from the PM. These could include testing specific functions to provide feedback for engineers, preparing applications for client demo testing, or even holding a demo session about a new feature. Additionally, they may review support tickets as well and assist the support team with testing. Before deployment, manual testers are often asked to conduct a thorough review of the application to ensure everything is functioning properly.

Their daily responsibilities include: 

• Testing project issues from the project boards.

• Logging new bug reports and issues in the Triage lists

• Attending daily meetings 

• Keeping an eye on Slack for updates or queries. 

• Performing a comprehensive walkthrough on deployment days to check critical user flows and to ensure that everything functions smoothly.

• Testing new features thoroughly.

“If there’s a deadline, that takes priority, along with any support requests or issues flagged by the project manager,” Alexa added.

Testing new features remains a priority, especially for projects with active development. Deadlines, ongoing development, and PM requests heavily influence task prioritization. For lower-priority tasks, such as support requests or stalled projects, testers shift their focus as needed while maintaining a balanced workload and efficient testing process.

Automation Testing Perspective

For automation testers like Filip, Rafal and Damian, the day starts with reviewing automated test runs. They check CI pipelines to ensure automation scripts run successfully, analyze test results, and log any failures.

“Maintaining existing test scripts and bug reporting have the highest priority. Adding new tests follows,” Damian explained.

Their routine consists of:

• Reviewing test results from automation runs.

• Attending daily stand-up meetings.

• Writing new automation scripts and fixing existing ones based on changing requirements.

• Performing exploratory testing when needed.
  

Communication and Collaboration

Communication is a cornerstone of QA. Dóra and Alexa interact daily with developers, project managers, often through daily meetings or direct messages on Slack. While QA collaborates less frequently with the UX/UI team, they engage when issues arise with design implementations or specific tickets. According to Filip, automation testers work more closely with developers on automation challenges.

“We talk with project managers and developers regularly, during daily meetings or via messages. With UX/UI, communication is less frequent, unless there’s an issue with a design or a FigJam that directly impacts testing,” Dóra shared.

When reporting bugs, our testers follow a structured process:

• Minor issues, such as typos are reported directly to developers.

• For more complex problems such as unclear bugs or missing design elements, they create tickets (with detailed reproduction steps and screenshots) or reach out to the responsible developer for clarification.

• Questions or ambiguities are often shared in Slack channels to gather input from the team.

Their collaboration within their team is equally dynamic. “When we work on the same project, we discuss issues and bugs and even review each other’s tasks, providing a fresh perspective. During tight deadlines or deployment days, we support each other by sharing tasks,” Dóra added.

Automation testers follow a similar approach, but focus on logging bugs in GitHub with detailed reproduction steps, logs, and videos.

“We collaborate by sharing knowledge, reviewing each other’s test cases, and running peer reviews for automation scripts,” Rafal noted.

While manual and automation testers don’t work together as frequently as before, they continue identifying areas where automation can optimize the process and improve efficiency. They also provide feedback on test scripts.

Manual testers, however, cooperate more closely with the documentation team at platformOS. They often inform technical writers in a Slack channel about changes and new feature implementations or hold demos to explain new functionalities. Technical writers also often reach out to QA testers for clarification on specific functions or features, ensuring smooth communication between engineers, testers and technical writers. This collaboration leads to a more accurate and comprehensive product documentation.

Tools and Technologies

QA testers rely on a variety of tools to perform their roles effectively. 

Among the most frequently used tools of manual testers are:

• Screen to GIF: A gif-making tool to visually demonstrate bugs or issues.

• BrowserStack: A platform to test websites across various devices and resolutions, simulating environments testers don’t have direct access to (e.g., tablets).

• Laptops & phones: Primary hardware used for testing, with occasional use of BrowserStack to replicate other views.

Our automation testers work with the following tools:

• Playwright & TestCafe – For handling automated tests in modern web apps.

• GitHub Actions & CI Tools – Running automated tests and integrating with development pipelines.

Alexa and Dóra also emphasized the importance of continuous learning. They attended a training program last year, Testing Bootcamp on Udemy, which significantly enhanced their skills. They expressed interest in delving deeper into automation testing, aiming to expand their expertise further. Filip, Rafal and Damian expressed interest in AI-powered testing tools, highlighting the importance of keeping up with emerging trends in automation.

Personal Insights and Reflections

What drives Dóra and Alexa in their roles as manual testers is the ability to improve others’ work and deliver high-quality products. At the same time, automation testers argue for problem-solving and improving testing efficiency.

“I love the visual aspect of testing and ensuring the design aligns perfectly with expectations,” Alexa said.

“I prefer functional testing—identifying logical errors. It’s fascinating how we complement each other in our strengths,” Dóra added.

"I enjoy the problem-solving aspect of automation, where you’re constantly improving testing efficiency," Filip shared.

For aspiring QA testers, they recommend developing strong communication skills. Providing feedback diplomatically is essential, as pointing out errors can be sensitive. Framing feedback as a collaborative effort helps foster teamwork and problem-solving.

“Pointing out errors can be sensitive, so it’s essential to approach the conversation diplomatically and focus on collaborative problem-solving,” Dóra explained.

They also encouraged aspiring testers to remain open to learning and to explore automation testing.  Broadening your skillset makes you more versatile and valuable in a QA role.

On the other hand, automation testers advise to start with manual testing, learn a programming language like JavaScript or Python, and practice writing small automation scripts. Understanding version control systems like Git is also essential.

Breaking Misconceptions

One common misconception about QA work is that it’s purely about finding faults. Our testers were quick to dispel this myth. In reality, QA requires a methodical and systematic approach that combines technical knowledge, problem-solving skills, and productive teamwork to guarantee a flawless user experience.

“Our goal is not just to find errors but to improve the product and ensure it’s the best version it can be for end users. It’s about contributing to the success of the team and the project,” they emphasized.

Conclusion

The work of QA testers might not always be in the spotlight, but it’s crucial to the success of any software product. Their attention to detail, effective communication, and dedication to quality ensure that the final product is not only functional but a joy for users to interact with. For those considering a career in QA, the field offers countless opportunities to grow, innovate, and contribute to building excellent products.