“He's making a list, And checking it twice.” - QA/Test Teams Make The Difference Between a Naughty or Nice Product Launch
It happens every day. You ask a development team for an estimate on a new feature or product. They throw some numbers at you - 6 weeks, maybe 2 months. Great. You map it out and start the project. The two month deadline approaches…and even with your built-in buffer, you have a last minute surprise. Testing is taking longer than expected!
Product testing is a crucial phase in the development of any software or digital product. It ensures that the product meets the desired quality standards and performs as expected. In this post, we'll explore the common processes, tools, and trends in product testing, explained in a way that even non-technical product team members may be able to follow. I also share some questions Product Managers should discuss with their Quality Assurance(QA)/test engineers to ensure thorough testing and alignment with the product vision.
Get To Know the Test Team
Most test teams consists of the following roles:
Quality Assurance(QA)/Test Engineers: These roles are responsible for working with the Product team to design and execute test cases, identifying and reporting bugs, and ensuring the quality of the software. They review the product testing requirements, review test plans, and ensure the released product meets both quality and user acceptance standards.
Automation Engineers: It is common in a lot of larger teams to have engineers who write and maintain automated test scripts to improve efficiency and coverage of testing.
Performance and Security Engineers: These are generally organization-wide roles who ensure overall performance and scalability of the software under various conditions. Security engineers are critical to ensure there is compliance with industry security standards, and running regular checks to identify (and rectify) vulnerabilities.
In addition, there are platforms commonly used by the teams that will be referenced through the development process. Best to get familiar with those tools. Some of the most commonly used apps by QA teams include :
Postman: Postman is an application that allows the testing of web APIs.
Jenkins: Jenkins is a Java-based open-source automation platform with plugins designed for continuous integration. It is used to continually create and test software projects, making it easier for developers and DevOps engineers to integrate changes to the project and for consumers to get a new build
Selenium: Selenium is one of the most, if not the most, popular open-source frameworks for web testing automation
Whenever I start on a new team or a new project with QA Engineers I have not worked with before, I make it a point to get to know. Some of the questions I ask them include -
What does a typical test plan look like for a new feature? This helps me understand the common testing approach and strategies; and also understand what I can provide the team for mutual success.
Are there potential risks or challenges in testing this feature? This helps me understand potential issues early in the process, and adapt the scope of work accordingly.
How are you prioritizing test cases? By asking this I can clarify and ensure testing efforts are focused on high-impact areas.
Are there any dependencies or integration points that need special attention? This ensures that all aspects of the feature are thoroughly tested, and I can also anticipate any situations where I may need to help unblock the team.
How can we improve collaboration between product management and the QA/test team? This is a question I would ask any team I work with. :) In all seriousness though, implementing a robust feedback loop between the testing team and the product management team can help identify and address issues early in the testing process, and minimize delays and interruptions to the release cycle.
In many instances, most Product Managers will likely coordinate with the Engineering Manager for updates on testing processes and roles. As with most technical aspects, it behooves Product Managers to understand these tools and why they are used, without necessarily knowing how to use them for QA tasks. Also, it is always best to know which person is performing these important roles as you go through the product development and launch processes for quick troubleshooting.
Best Practices
To ensure effective testing before releasing a product, there are some standard checklist items a good Product Manager can do.
Starting testing early in the development process is crucial. For example, in the case of developing a new e-commerce website, testing should begin as soon as the basic website functionalities are available, such as browsing products and adding them to the cart. This early testing helps identify and rectify issues before they escalate, ensuring a smoother product launch.
Define clear test objectives and use-cases. Ideally this documentation has already been created before any code-writing has commenced, so that the test team can create the right scenarios. For instance, if developing a healthcare app that tracks users' fitness goals, the test objectives should include verifying that the app accurately records and displays fitness data, such as steps taken and calories burned. Defining these objectives helps focus testing efforts and ensures that all critical aspects of the product are thoroughly tested.
Ultimately, collaboration across teams is essential to get the desired outcomes from the QA process. In developing any new software, close collaboration between the development team, testing team, and project leaders on the Engineering and Product side ensures that all aspects of the software, including functionality, performance, and usability, are adequately tested and validated.
Build and Launch with Confidence
When you pack for a trip, you make a list, you check it twice before leaving your house. This ensures a stress-free, smooth, and somewhat predictable experience when taking on a new experience. I think investing in the test process enables you to do the same when you release any new improvements, features, or products into the market. That’s not to say unexpected things wont happen — but atleast you’ve planned ahead by avoiding any reasonably possible pitfalls.
By adopting best practices such as starting testing early, defining clear test objectives, using a variety of testing techniques, and collaborating effectively across teams, product managers can help minimize common errors and deliver high-quality products to market. Assigning priority and reasonable estimates to testing (that also release pressure from marketing or business deadlines) can contribute significantly to the success of delivered products and the satisfaction of their customers.
