I am looking to build out a testing team and ultimately leverage automated testing, but I truly don't know how or where to begin this journey. If you have experience in this space, where did you begin?

3.3k viewscircle icon3 Comments
Sort by:
Head of Technical Delivery Services in Travel and Hospitality2 years ago

The manual process of creating QA artifacts and setting up a robust and long-term QA strategy is first thing needed to establish a QA practice from scratch. Once Manual QA is in place and members have gone through few rounds of manual regression and product maturity is there as well, automation can be started. The choice of how much automation can be developed will be areas that need more effort or undergo frequent changes etc. 

Strategic Banking IT advisor in Banking2 years ago

We've been through the same path a few years ago.

We first found out that we were very weak with testing (either manual or automated) and that was leading to more and more defect in production.

We looked at 2 strategies:
A) Increase code-coverage testing and make it mandatory.   You cannot promote / deploy your code if you don't reach 80% of code-coverage with your tests.   We have a tool that measure this.  [we are using Jenkins]
B) Automate regression tests  [we are using HP-ALM/QC]

As we had around 20 teams (+/ 1,000 developers back then), we put in place a new team that would:
A) define best practices
B) make sure the right tools are available
C) become a center of excellence (testing champions)
D) measure results

The goal was not to keep that team forever.  After 3 years, all the best practices have been absorbed by the 20+ teams.  They now have incorporated the automated testing practices in their daily tasks. 

Hope it helps.

Steve

Solutions Architect in Software2 years ago

A solid starting point is to begin with Manual QA, where you'll create comprehensive test plans and test cases. This approach will provide you with a clear understanding of what can and should be automated. It will also help you assess the potential benefits and cost reduction associated with automation. In the early stages of software development, when frequent pivots are common, relying solely on automated tests might become burdensome due to the need for constant updates. Therefore, striking the right balance between manual and automated testing is crucial for an effective testing strategy. As the product stabilizes and requirements become more predictable, you can gradually introduce automated testing to streamline the process and improve overall efficiency. Remember that each testing approach has its strengths, and a thoughtful combination of both manual and automated testing will yield the best results for your testing team.

Content you might like

We are currently using AI in our contact center19%

Our data is not easily/fully accessible between departments42%

We use conversational AI for web chats, but not for telephony20%

We just can't justify the investment16%

Other (please comment)1%

View Results

We partner closely with design, but not with marketing26%

We partner closely with marketing, but not design53%

We partner closely with design and marketing16%

We do not partner closely with either3%

View Results