Automation testing has quickly become a necessary staple for most projects in order to remove risk and ensure quality. With the industry move to Agile development, shorter iterations also means a quicker turn-around required from the testing team. To maintain reasonable levels of regression and other types of testing, automation has become vital to ensure accurate and timely completion.

At Xpanxion, automation is a deep and mature practice that has been imbedded into almost all of our teams because we recognize the value. A properly automated regression suite of 500 test cases can be executed over ten times faster than a manual tester. This means greater coverage allowing team members to focus on more important and critical items. We are built to adapt to any project and are versed in various tools to perform in the environment at hand. Below are some of the tools in which we are proficient.

  • Selenium Web Driver
  • Cucumber
  • Test Complete
  • SoapUI
  • Visual Studio
  • Sikuli
  • Quick Test Pro / Unified Functional Testing

While all have different competences, we prefer open source tools from which we can develop tests directly against the source code. This allows less rework meaning the automation developer can further expand the coverage of their tests. To support our code, we have developed our own internal framework from which we can leverage commonly executed tests to further increase our efficiency. Our automation staff are skilled developers who understand the core principles of quality assurance and are versed in many languages as well as object oriented programming. Our practice is adaptable to almost any tech stack or environment, but here are some languages our automation experts have in their tool belt:

  • Java
  • C#
  • Ruby
  • JavaScript
  • VBS
  • HTML5/CSS3

Our automation personnel first engage with a high level understanding of the project and business goals at stake. We find this necessary in order to prioritize and provide value to reach those goals. High level documentation such as test strategies, test plans, and other artifacts are created to further support that effort. Development of automated test cases then quickly begins to start the build out of a test suite. This is followed by regular maintenance to keep the tests relevant and ready to kick off as soon as development is ready for testing. The efficiency of automation is hard to ignore and is a must for any development team.