Creating a bug-free software is hard, to the extent that it seems like a myth. Bugs in software represent the discrepancy between the expected and actual behaviour of the software. Although it’s unrealistic to make software bug-free, efforts can surely be made to minimize the number of bugs in software through various prevention and detection techniques. Prevention techniques are the ones that can be used to prevent bugs from occurring in the software.

To follow up on my previous article, Guide to Testing Automation with Robot Framework, I will go into more detail about the overall process of writing automated Robot Framework test cases and how to track automation in Jira using Xray. Test automation may seem hard, but it gets easier with the right tools and an open and helpful community like the one surrounding Robot Framework. If your team is using Jira, you can easily integrate testing results coming from the CI/CD pipeline.

As Agile methodology was introduced, the need for fast and continuous delivery of software applications increased. Fulfilling this need, automation testing within organizations increased. Various free open source and paid automation testing tools were introduced. Selenium was the first open-source automation tool introduced and organizations moved towards this tool for their test automation needs.

All good things need to come to an end. In this case, that’s true of the Sauce Sample Test Frameworks GitHub organization. While these sample frameworks are now gone, they’re not forgotten. In fact, we’ve replaced them with something better. In the past, this organization provided barebones examples of connecting to Sauce Labs with sample frameworks in a large variety of languages and tools. These frameworks were mainly based on Selenium and testing a basic web page.

Robot Framework is a generic open-source automation framework for acceptance testing, acceptance test-driven development (ATDD), and robotic process automation (RPA). Robot Framework allows testers to easily write automated test scripts using a keyword-driven testing approach. Teams using Jira and Xray can easily integrate testing results coming from the CI/CD pipeline. This provides a lean and scalable test automation process.

JMeter has many plug-ins and downloadable JAR Files you can use to support your testing, it is also possible to write your own custom Jar files and use these as well. Why would you want to do that, you may say, well whilst it is unlikely that you would need to create anything too complicated. You may feel the need to create utilities to support your own in-house performance testing or just something to make your testing process easier.

Selenium was first released in the mid-2000s as a Web browser extension for recording and playing back interactions with Web browsers. Since then, it has become arguably the most popular tool for test automation. In a survey of the automation testing community, the framework has been used by more than 80% of those surveyed. Selenium is an open-source framework for Web-based application automation that includes Selenium WebDriver, Selenium IDE, and Selenium Grid.

Here we are for yet another new release of OctoPerf. We’ve actually released two minor versions since the last update post, but this time we will also release a long awaited feature, Microsoft Azure on demand load generators!

Developers make fun of legacy systems because we're scared of them. We're afraid that the tiniest change will cause the app to break in unexpected ways. We're afraid we won't realize it until a customer complains. One way to combat this fear is through testing. In this article, José Manuel shows us how to retrofit legacy systems with acceptance test suites so we can maintain them with less fear and more confidence.

Katalon Studio has released its latest version 7.5 that comes with the new Native Windows Recorder feature. The testing tool provides its users with a comprehensive Recorder utility, helping them to generate test cases quickly and accurately, with minimal effort. This article will look into the nature of desktop application testing, its relevance in today’s age, and how you can best utilize the tool for all types of application testing, cross-functional, and robustly executed.

In today’s online world, every digital experience is a reflection of your brand—which is why mobile application testing should be at the forefront of your testing strategy. Whether it’s a picture of a check, a selfie, or a QR code, images can be uploaded to mobile apps for many reasons. Behind the scenes, the application has to do some amount of processing and storage.

Digital confidence, the feeling that everyone in your organization expects your application to work exactly as it was designed, is a journey that requires a number of strategic and tactical considerations. From cultural buy-in from the top to tooling and resources that help support continuous testing at scale, there are a number of things that can help build confidence that your applications are providing flawless user experiences.

Behaviour-driven development, also called BDD, is a methodology that involves developing software through examples and provides collaboration between different stakeholders on the team. Stakeholders on a SDLC team are a mixture of technical and non-technical people. BDD encourages all team members to work closely using a common, non-technical language to set the expectations and behavior of a feature. Because of BDD, they share a common understanding of the work that they have to deliver.

The BDD tool, Cucumber has a frontend that is written in natural language and reduces the dependencies on developers for the construction of an automated framework. Testsigma is an automated testing tool that further reduces the dependency on developers by removing the programming language’s extensive backend. With the help of these tools, developers can now focus on feature development better and need not worry about automating the tests.

As outlined in our rebranding announcement post from Feb 24th, today we're disabling access to v4 projects in the LoadImpact web app at app.loadimpact.com (v3 projects will continue to be available until Dec 31st, 2020). All v4 projects, tests, and test results will henceforth only be accessible from app.k6.io. The same login credentials are valid across the two web apps. Rest assured, no data is going away, it's technically an older of two frontends being sunsetted.