The latest News and Information on Software Testing and related technologies.
Your mileage may vary on Ryan Gosling films. I happen to be a fan, and I always chuckle during the climactic scene in The Notebook. Drenched in rain, Gosling says to Rachel McAdams’ character, “It wasn’t over. It still isn’t over.” He of course is talking about their relationship, but I could easily draw a parallel here with testing. While in the past it may have seemed that a tester’s job was done once code was pushed into production, that is no longer the case.
Recently we had a chance to work with several software testing teams to help them get started with their test automation endeavors. The teams consist of mostly manual testers, and some who had experience with test automation before, but none of them were familiar with programming like developers. The applications are mostly web based, with companion mobile apps.
Here at LoadFocus we provide an easy way of running your custom JMeter scripts from the cloud from various locations and with more than 20.000 users in parallel against non-secured and secured APIs.
One of the most important aspects of automated web application testing is having a good grasp of using locators. Locators allow retrieving DOM elements from the web page. Interacting with web elements during automated tests allows to create end-to-end tests that simulate real users behavior. In this blog post, we will talk about two types of locators – CSS selectors and XPath.
From the traditional Waterfall model to more iterative approaches like Agile and DevOps, software testing is constantly evolving. And while teams have worked their way to deliver quality at speed, there seems to be something holding them back. Read on to learn about in-sprint automation and why it’s the key to moving at DevOps speed.