Bug Blog

The UK government is demanding answers from Royal Bank of Scotland and Barclays after yet more technical glitches locked customers out of their online banking accounts last week.

Thousands of shoppers in the United Kingdom were hit with duplicate debit card charges after a technical glitch caused a major payment processor to run some transactions twice.

Wells Fargo admitted that because of a computer glitch, nearly 400 of their customers were foreclosed on between April 2010 and October 2015.

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.

While other big companies like Facebook and Google cash in on monetising user data and pitching heavily targeted advertisements, Apple's latest release is taking steps to protect their users' browsing habits and personal information.

The insurance industry is on the cusp of massive disruption. For the longest time the industry was made up of traditional offline corporations that followed a paper and people heavy model, and largely resisted the changes which upended other industries through the last decade or so.

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.

Exploratory testing is a discovery process to determine what does and does not work with regard to a particular software application or website. It is a self actuated process in that it is the tester who determines what to test and is in charge of the exploration.

There was a point in the 1980s where some American banks considered the customer to be nothing more than a source of revenue. In fact, certain banks went out of their way to discourage what they called "small revenue clients." Fees were raised in an effort to discourage small customers. The idea was that if small customers where nickeled and dimed enough, they would be sufficiently annoyed to go somewhere else.

When done right, test automation can lead to significant efficiency and cost improvements. Unfortunately, many organisations fail to maximise the full potential of their automation program due to a number of common challenges. Here's how to overcome them...

You'll be showing your age if you know that RPG once stood for something besides Role Playing Game. It once stood for Report Program Generator, a programming language, of sorts. Or, as the programmers of the day would joke, Really Poor Graphics - because it had no graphics at all. But that was in the age when computer programming consisted mostly of filling out forms. So, checking the code was often just a matter of proofreading the form. Still, there was some actual functional testing done.

Creating quality test case scenarios requires knowing what you are testing for and why, as well as the user requirements and what the application is designed to do. Once these things are known, it then becomes possible to write effective testing scenarios.