Systems | Development | Analytics | API | Testing

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.

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.

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.

Apache JMeter is a Java open source tool. If you want to run load or performance tests using Apache JMeter, you can use their Graphic User Interface (GUI) and you don’t need to know any programming language, follow the JMeter documentation and you are ready to go to design your API testing scenarios.

As the lead of the Selenium project, I wanted to kick off a new blog series leading up to the release of Selenium 4. During this series, I’ll talk all about how the Selenium project works, who is involved, how you—yes, you!—can get involved, and we’ll get a sneak peek at what’s new in Selenium 4. I've been speaking about this off and on for a while, but now the 4.0 release is looming I wanted to start sharing in more depth.