You say to-MAY-toe, I say to-MAH-toe. I hear the questions daily - "Did you validate the system? Did you verify the feature?" The words validate and verify are used interchangeably, but what do they really mean? Is there a difference? In the world of software development and quality assurance, yes… and you need to do both.
Behavior-driven development (BDD) is an Agile software development process encouraging collaboration between developers, QA and non-technical participants in a software project. Cucumber is an example of a JavaScript (JS) methodology that enables BDD. It helps to lay a test automation foundation by embracing coding standards and design patterns that will be used in the automation development process.
Frequent software delivery drives innovation. According to the State of DevOps Report, high-performing organizations deploy 200x more frequently and have 3x lower change failure rates than lower-performing organizations.This type of velocity and scale is only possible for a highly capable engineering team with an advanced DevOps infrastructure. However, legacy and startup organizations may have a harder time accomplishing this.
I’ve been testing software professionally since 2001, when I was in my late 20s—when my eyesight was perfect. As I’ve gotten older, I’ve struggled with whether to make the font bigger on my web browser or phone, or to carry my reading glasses everywhere I go. I have to make this choice because some web sites were developed to account for this, and some weren’t. As I get older, this problem is only going to get worse.
Testing any software project is an important step in order to find out how the software functions. Learning when the project acts as expected (and when it does not) is the ultimate goal of the testing process. Testing stops design errors from reaching production code. However, testing should not only happen before code is deployed.
Today is a great day at Sauce Labs! We just announced that we’ve acquired Backtrace, a provider of best-in-class error monitoring solutions for software developers and engineers. Backtrace enables organizations to mitigate application risk and improve digital quality by empowering development teams to rapidly deploy code with confidence knowing that they can quickly identify and remediate bugs once in production.
As far as web test automation goes, Selenium is certainly the most popular toolset. That popularity is uncontested. A survey on test automation finding that 54% of the respondents were using Selenium might be surprising only in that the number is so low. Many of the alternatives to Selenium, Software-as-a-Service products that record and re-run entirely in the browser, still use the Selenium as the core driving technology.
A critical decision for organizations that are defining their automated testing strategy is choosing the right automated testing framework that will help their development and QA teams efficiently write and execute automated tests. The market offers a plethora of frameworks to choose from, and the decision isn’t always easy.
Automated testing for web apps has been around for well over a decade. For much of that time, Selenium has reigned supreme as the go-to testing framework for virtually any type of testing need that involves a browser-based app. But as the world of test automation continues to evolve, newer tools have emerged. Chief among them is Cypress, a testing framework that is becoming an increasingly popular alternative to Selenium. Is Selenium or Cypress a better choice for your automated testing needs?
JavaScript consistently ranks as the world’s most popular programming language among developers. It should come as no surprise, then, that a variety of JavaScript test automation frameworks are available to help developers test JavaScript apps. Here’s a look at the top five such frameworks, with tips on the pros and cons of each.
