The world is witnessing the rise of Agile methodologies in software development. They require a new approach to software testing, which must well align with the nature of Agile, a fast-moving philosophy. Test automation was not born to serve Agile teams, however, it makes Agile testing- a crucial part of the Agile concept- achievable. This article shows all essentials for the implementation of automation testing for Agile teams.

In our last post, we looked at the multiple layers of testing and where UI tests fit into your overall architecture. In case you didn’t read it, here’s a TLDR: Testing architecture can be grouped into 3 “layers”: Layer 1 tests tiny chunks of code in complete isolation. Layer 2 tests larger pieces of code in partial isolation.

The landscape of software testing is changing. In the hyper-competitive world of technology, speed and quality are often seen as opposing forces. We are told to “move fast and break things” if we are to succeed in getting our products into the hands of users before our competition beats us to the punch. This often times means sacrificing quality and confidence in the name of getting new features out the door.

Is your team able to pivot with changing demands, accelerate new features, and provide the highest product quality? Being agile allows you to move fast, make changes, and keep quality at the center of your work. Xray empowers your team to strive towards continuous improvement, optimize testing efforts and exceed quality goals with features and workflows that support agile methodologies.

Deep in the implementation of every automated UI test lives the potential to turn something simple into something slow and unreliable—simply by adding extra Selenium commands. The data clearly show that longer tests are less likely to pass. In this case study, I will show you how to optimize a test and make it 560% faster. We will do this by tackling inefficient use of Selenium commands.