Having a test suite containing thousands of tests introduces the possibility of creating bottlenecks in the software development process. Having all of those tests can come at the expense of slower development and testing times. However, it's not all sunshine and rainbows. The higher the test coverage your application tends to have, the more confident the team becomes in shipping quickly. The good and the bad of automated testingĪny testers or developers working with a robust automated test suite can tell you how it provides the peace of mind to deliver high-quality products. We needed to think of a solution to keep providing value to the team, which would yield a better overall product. But as time rolled on and the test suite expanded, we found ourselves at this point where the tests were becoming a burden. I integrated with the QA team for a few weeks to get them started, setting up the frameworks and training team members without automation experiences.Ī few months into our work, regression testing times took less than two days to complete, and the rate of reported bugs in production dropped by over 50 percent. It was a large project, and each sprint took the team over a week to thoroughly test, given the number of bugs that constantly crept up during active development. I was in this meeting because a few months earlier, I was the one who began the initiative to improve our test automation, primarily because we had no strategy whatsoever. I don't know what we can do to help development besides stopping." We've added a ton of tests, and it's helped the testing team a lot. "We're doing what we've been tasked with-implementing automated tests to help us reduce the time it was taking the team to complete each sprint. The QA engineering lead was understandably not pleased hearing about this. "They're not happy with how long it's taking our continuous integration system to build between their commits and have begun doing things to bypass the consistent test runs, which don't help your efforts." I knew this pain all too well since I experienced it myself during my daily work. "Our developers have been complaining about the test suite", said the tech lead after we started our talk. Along with me were the product's tech lead and QA engineering lead, and we scheduled this meeting to discuss an emerging issue happening on the development side of things. Years ago, I found myself sitting in a small conference room at the office of the startup I worked at as a software engineer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |