You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
What is quality assurance?
Quality assurance (QA) is any systematic process of defining whether a product or service meets specified requirements.
It is defined as part of quality management that ensures that requirements will be fulfilled. Quality assurance is twofold – internally to management and externally to customers and third parties.
Quality assurance aims to fulfill front- and back-end processes competently and fluidly; by delivering the intended product or service on time and within budget and going above and beyond in all transactions and interactions with the consumer.
Contrary to what circulates about the roles and responsibilities of the QA team regarding product quality before or after software deployment, it is of utmost importance that the whole team is responsible for product quality. The best practice is for development and testing to go in parallel. When this is not the case, discrepancies and interruptions will occur, leading to poor product quality.
There are three primary stages in product development, where we will be discussing the primary responsibilities of the QA team in each step.
1. Initial Stage
2. Product Development Stage
3. Supporting and Scaling Stage
The most important responsibility for the QA in the initial stage is product requirements analysis.
A bug discovered at this stage is five times less costly before product development and ten times less costly than a bug found at deployment.
At the product development stage, the QA role will include but not be limited to the below six significant responsibilities.
ensure features comply with technical and business requirements
set up a proper quality management system
select tools for manual and automated testing
Create autotests for specific parts of the system
Maintain documentation and system description
Inform about release dates and organize product demos
When it comes to the supporting and scaling phase, the significant responsibility of the QA engineer is dealing with four major players:
Analyses user customer experience, gather feedback and compare user interaction with a planned journey.
develops for product owner detailed acceptance criteria for user stories, modify or improve existing user stories by providing feedback about testing experience and collecting feedback from the product owner.
Informs the development team about the discovered issues and bugs, monitors bug fixing, and makes sure that users no longer face problems.
Presents ideas and insights to the development team generated by the analysis, so they can be added to the backlog if approved.
In a competitive market for software development, stand out by giving a quality product. Fortunately, quality assurance works in boosting client confidence, especially when you are looking to build long-term relationships and customer loyalty. Quality assurance prevents corporate emergencies, particularly when implementing testing that guarantees no room for errors. And most importantly, it saves you money and effort. A faulty application might cost your client a fortune. Proper QA testing will allow the discovery of potential bugs or issues that might occur in the future.
Andreas Springer _Actonic_
Head of Marketing
2 accepted answers