Bug Blog

An Australian retailer with over 50 stores was upgrading its e-commerce platform and hiring a full-time software testing lead.

Bugwolf, a leader in software testing, announces today that we have partnered with UiPath, the leading enterprise in Robotic Process Automation (RPA) software company, to improve software testing with the power of AI, machine learning, and robotic automation.

Our cultural values are at the core of everything we do and the way we engage with our clients, employees, and suppliers.

Pulling off a win was a long shot, but New Jersey gambler Anthony Prince placed a $110 bet on the Broncos at the FanDuel Sportsbook over the counter at the Meadowlands Racetrack.

It has been reported that five winners missed out on claiming million-pound prizes due to Camelot's errors in posting Lotto results, out of dozens of prize results that were omitted from publication.

Access a detailed UAT guide packed with free templates and tips for start-to-finish user acceptance testing success. Discover how to build UAT teams, plan for UAT and how to manage results. Download the free guide - no opt-in required.

If you’re curious to see which bugs most commonly fly under the radar of traditional testing teams, you’re in luck... our latest infographic summarises the results from every Bugwolf challenge in Q1 of 2017 to reveal the most elusive bugs by device, operating system and bug type.

A team of skilled software testers is a huge competitive advantage for any organisation. In this infographic we reveal Bugwolf's time-proven philosophy for attracting the best testing talent, including the exact job ad we use when we need to find A-grade testers.

How often should you test? Naturally, that depends on the risk profile and scope of the release, but the short answer is this... you should test as many times as it takes to give you confidence that your software is working as expected, every time, within your desired specifications. In practical terms, that equates to at least one test while the release is in pre-production, another in pre-production after the staging bugs have been remedied and one in production.

Developing test cases is one of the very first steps taken in testing, before any testing is actually done. And the quality of the cases developed will have a strong influence on the success of the testing cycle. This is why it is important to know how to write test cases that will lead to a successful outcome. And so, executing quality test cases is a vital element in software testing. This is why knowing how to write effective test cases is so very important. It's a matter of following the principles involved.

Change is one of the few constants in the world of software testing. An organisation’s ability to stay on the front foot and adapt to evolving development environments and consumer expectations has implications that stretch far beyond the IT department. 

The business environment is changing. Economies are no longer as stable as they once were and so there is far less tolerance of risk than there used to be. Quality assurance has become a focal point for business expansion as businesses try to attract and retain customers by improving service while cutting costs. Software applications in the financial sector in particular, and other areas as well, are now a vital part of customer interaction and retention. This means that companies are demanding faster development cycles while being less tolerant of failure, which is one of the main reasons why agile development is so popular.