Let’s Talk About Software Testing and Test Automation

Real-world examples of automancery at companies like yours

This is the core service offering that Arch DevOps was founded on, but we haven’t stopped here! Software testing eats thousands of man hours per year. But it doesn’t have to. Read about the ways we’ve solved this challenge simply for multimillion and multibillion dollar companies for years.

Test Automation Code Cleanup

Challenge: A team at a multibillion dollar company previously had a consultancy come in and write a bunch of test automation. But it was written quickly since it was a fixed-bid project, and there was a lot of near-duplicate code

Solution: First, an assessment was done of the current automation codebase. It was determined that there were some patterns showing up with how those near-duplicate chunks of code were being used. From there, a piece of automation was created to remove one of the near-duplicate chunks and then re-run just the tests that used that chunk. If any of the tests failed, the change was put back to what it was. But if they all passed? Then that updated code got pushed up to the code repository for everyone to use.

Result: The changes this particular automation made were pretty transparent. Over time, the code just became cleaner after about a week of this bot running in the background, making small changes and pushing up safe modifications. It resulted in freeing up thousands of lines of code that no longer had to be maintained, and the desired logic was kept intact. Slow and steady wins the race!


Framework Creation and Coaching

Challenge: Companies that find their testing effort takes too long can get in a bind. Most software testers don’t write software–and that’s fine. But couple that with a natural fear that automation may take their job, and success can be a delicate thing to achieve.

Solution: We’ve got a history of creating simple, easy-to-use test frameworks that allow people to write their automated tests in plain English. But we don’t stop there, because we also create training curriculum for the current staff and any future staff to get ramped up on, so that new hires on the testing team can start being effective with automation right away.

Result: Our work actually lowers the technical bar that usually comes from adopting automation. Instead of hiring the rare-to-find tester/automation people that are usually more expensive, companies can continue to hire people for skill in QA. Plus, when testers know they can come to a company and learn automation, it makes finding talent much easier since it’s a sought after skill.