Bug Blog

Quality Assurance (QA) is a critical aspect of software development that ensures the end product is as bug-free, functional, and user-friendly as possible. One of the most critical elements of QA is test case design. Writing effective test cases can not only help in identifying defects early but also play a crucial role in optimising the testing effort for time and resource efficiency.

Earlier this year, Wells Fargo disclosed that almost 400 of their customers were foreclosed on due to a computer error. This week, they revealed that an expanded review identified 145 additional customers who lost their homes due to the glitch.

Some Apple Watch users discovered that daylight savings time had sent their device into an endless loop of crashing and rebooting.

In the latest of a string of new mobile devices to hit the market in 2018, Samsung has introduced the Galaxy Note 9, adding ever-growing complexity to the compatibility requirements of digital teams.

Every digital leader knows the importance of rigorously testing websites and apps before release… This infographic demonstrates why it is crucial to test digital apps and websites even after launch.

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.

Did you know that professional UAT teams can add significant value to new releases, even before a single line of code has been written? It’s true. Senior digital leaders are increasingly turning to user acceptance teams with the hope of uncovering critical product insights during the planning stage of the SDLC - not to review their own software, but rather the software of others in your market (and beyond).

There are 1/4 million 911 calls placed in the United States every day and most of them get through. So the System Works pretty well. However, it can be stressful and even frightening when someone calls 911 and no one picks up on the other end. Such problems have happened in both Denver and Dallas.

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.

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. 

When most people think of software testing they generally visualize functional testing. Functional testing is concerned with how well a system executes its intended functions. These functions may include integrations, business processes, searches or data manipulation as well as the execution of commands. While non-functional testing is more interested in how the product behaves rather than what the product does.

Testing against browser update begins with a quality suite of test case scenarios. The purpose is to be prepared ahead of time in order to make certain that testing can move forward even under high demand situations where quick turnaround is required.