Achieving top quality in a project takes more than just skilled Business Analysts, System Analysts, Developers, and UX/UI Designers. Quality Assurance (QA) is also essential. QA oversees every process from beginning to end, making sure each deliverable meets client requirements and quality standards.
The presence of QA in a project ensures the delivered work is rated 100%, building client trust. In this article, we had the opportunity to sit down with two seasoned QA experts from Bluebik Digital: Boss, Senior Software Tester, and Jean, Senior Customer Experience Assurance. Bluebik Digital is the latest business unit under Bluebik Group, dedicated to elevating the quality of digital transformation services, including system development, applications, and solutions. Although Boss and Jean have different roles, both have broad QA experience in many industries.
What makes a good QA professional? What mindset and attention to detail are needed? How do Manual and Automated testing differ? And what does the future hold for QA in the digital age? Let’s explore the experiences and insights of Boss and Jean.
QA in Every Project: An Indispensable Role in IT Projects
“Being a QA isn’t just about finding bugs. We’re responsible for ensuring the system’s quality from start to finish, delivering exactly what the client needs. It must be functioning, stable, and scalable for the long term,” explains Boss, outlining the core responsibilities of a QA.
“QA doesn’t come into the project once the developers are done coding. From day one, we are involved in understanding the client’s requirements and business flow. Then we plan the testing phases, design Test Cases, Test Scenarios, and Test Data. Once designed, the testing begins, followed by communication with the team to address risks and ensure the system’s quality,” he continues.
“Simply put, we act as the final checkpoint before the system is released to end users,” Boss adds.
QA is a crucial role that ensures all potential issues are identified and resolved from the start to finish of a project. The testing process includes four phases:
- SIT (System Integration Test): This phase checks how the front end and back end work together, as well as how the system interacts with other internal and external systems.
- UAT (User Acceptance Test): This step lets clients or users confirm that the system meets their original requirements.
- Performance Test: This phase checks how well the system performs, such as ensuring logins occur within 2 seconds and that the system can handle heavy traffic.
- PVT (Production Verification Test): The final test in a live environment to ensure the system works as expected after deployment.
While every project goes through these four stages, Boss appreciates the variety of industries Bluebik works with. “It’s about learning new things all the time. Bluebik takes on a wide range of projects, so we don’t focus on just one product. Recently, I’ve worked on electric vehicle charging technology. This project is different because we usually test apps or websites, but here, we also have to test the charging stations themselves. It’s exciting work.”
Manual vs Automated Testing: What’s the Difference, and How Do They Work Together?
QA uses two main testing methods: Manual Testing and Automated Testing. Boss mostly does Manual Testing, checking each step by hand against the test cases. Still, every project also uses Automated Testing. Jean, who specializes in Automated Testing, explains the differences:
“In Automated Testing, we start by creating project plans and designing Test Cases, just like Manual Testing. However, the key difference is that we develop a program to test the system, rather than using human eyes. After testing, our program generates reports that are shared with the client. At the same time, Manual Testing also collects results to share with the client. Once testing is complete, we demonstrate the system to the client, walk through different scenarios, and then provide user training,” explains Jean.
In short, Automated Testing means writing a program to test different parts of the project. This approach requires coding skills, which are important for anyone working in Automated Testing. Jean adds:
“The benefit of Manual Testing is that it allows us to easily adjust the Test or Scenario whenever there’s a change in requirements. On the other hand, for Automated Testing, changing requirements means we need to redesign the entire testing program. However, once the program is written, it can be used indefinitely. If there’s a change that affects the system, automation makes testing easier since we can simply rerun the automated tests.”
For Jean, the fun of being an Automated Tester began with curiosity during her studies. “Back then, professors typically pushed students towards Developer roles, but when I learned about QA, I was intrigued. When I tried it during an internship, I discovered automated testing, which made things much easier and allowed me to use my coding skills. That’s when I decided to pursue this path.”
The Bluebik Approach to Quality Assurance
Jean defines quality assurance as “quality that is accurate, satisfying, and appropriate. ‘Accurate’ means meeting the client’s original requirements. ‘Satisfying’ refers to the client’s impression of the final product, and ‘appropriate’ means aligning the product with the price they paid.”
Boss shares a similar view, stating, “To me, quality is defined by three key elements: accuracy, experience, and trust. Accuracy means the work meets the client’s requirements and business flow. ‘Experience’ refers to how easy, fast, and smooth the system is to use. Finally, ‘trust’ means the system must be secure and reliable, and capable of scaling as needed.”
At Bluebik, we focus on clear, measurable standards. We use a Definition of Done to set criteria for functional, non-functional, and acceptance requirements. We also use a Traceability Matrix to track quality metrics such as defect severity, test coverage, and test reports. This information helps stakeholders decide if the system is ready for release or if there are issues that could affect the client’s business.
As Boss further explains, “Our approach involves designing testing methods that are tailored to each project’s unique factors, including technology, risks, people, and client expectations. The challenge is rewarding, as we constantly learn new things and see our work having a significant impact on a national level.”
QA’s Eyes and Experiences: The Critical Attention of a QA Professional
When asked what qualities a good QA should possess, Boss emphasizes, “You must have a curious eye and constantly ask questions. We can’t just assume a system works perfectly until it’s been proven. We need to adopt the end-user’s perspective and also understand the client’s business to design precise testing. Additionally, technical insight is essential for communicating with the team when problems arise and for devising solutions together. These three perspectives are crucial.”
Jean also stresses the importance of meticulousness. “The most important quality is attention to detail and adaptability in testing. Some tasks can be automated, which saves time, but it’s essential to adapt and find creative solutions. For instance, we can automate a process that’s repetitive or convert a Manual test into a script for Automation.”
Another crucial aspect of QA that Jeanhighlights is the ability to catch small details. “Sometimes the design team may specify that text should be bold, but the system doesn’t display it as such. While Automation may miss this, QA must catch it. It’s about seeing those small details that can make a big difference.”
Addressing Errors: The QA Mindset
So, how do QA professionals handle errors? Boss explains, “We need to communicate with the team and align on how a mistake might impact the client’s business. We don’t blame anyone, but we need a plan to fix the issue within a specific time frame. A unified mindset and team ownership are key to effective work.”
Jean adds, “Soft skills are essential in QA because what we think might be correct may not always be the case. Communication with all teams is vital, and we need to approach situations with flexibility and adaptability.”
The Future of QA: AI Will Enhance, Not Replace
In an era where AI is increasingly integrated into the workplace, the role of AI in QA becomes an essential discussion. Jean believes that AI still needs to improve its “understanding.” “Understanding is crucial. Even humans need to comprehend things deeply. Training AI models to meet our needs takes time and expertise. But we can use AI for repetitive tasks, such as validating input fields with predictable patterns. This saves time in some areas.”
Boss adds, “Currently, AI can’t match human judgment, particularly in terms of ‘feeling’. For example, AI might not recognize that a two-second load time feels slow to users. Also, certain errors might not arise from business logic but from user experience, like text size being too small for seniors. These require a human eye for detection.”
Both agree that AI will never replace QA. As Boss puts it, “QA relies on human experience and judgment. AI will assist, but it can never replace the role of a skilled QA professional.”
This article highlights how important QA is for quality and shows the need for adaptability, technical skills, and human judgment in today’s fast-changing tech world. If you’re a tech-savvy professional who values quality, Bluebik Digital is a place to grow your skills and work on projects that make a real impact.
