< Insights & Interviews

High Profile Software Crashes!!

Keeping up with the latest and greatest external technology can be tricky for even the largest businesses in the market today. However, from an internal point of view, you would think that adequate software testing would eliminate any risks and problems before it's implemented.

Nonetheless, there have been several high-profile examples of businesses implementing internal software too quickly and causing problems for themselves and in some cases, the wider community.

TTC is committed to providing general and specialised testing services and solutions in both New Zealand and Asia. As such, we can take advantage of smart processes and technology to ensure businesses utilise software that meets the requirements of both the end user and internal stakeholders.

Here are three examples where better software testing practices would have made a significant difference :

1) Swiss Bank - 2014

When it comes to privacy, consumers expect banks to adhere to the best software systems possible to protect their data and information. However, in early 2014, some Swiss Bank customers received both their own end-of-year bank statement and number belonging to other people. Not only did they see bank account information, each statement contained addresses and names - potentially opening up customers to privacy breaches.

It was confirmed that the software system had a glitch which lead the problem. While this can be easily fixed, the Swiss Bank may have found the issue earlier by overloading the system during software testing. This is a true way of ensuring the software can handle periods of high demand.

2) Delta Airlines - 2014

Given the complex security features that airlines now impose on passengers, the Delta Airlines case last year raises a couple of issues. A hacker discovered that they could share the URL of their boarding pass and make it accessible to someone else.

At this point, they changed a single digit of the URL and realised that they had access to other passengers' boarding passes on the same flight. A typical boarding pass provides information on booking data, personal addresses and names and even passport names. Delta were quick to fix the problem, but given the ease of this hack, it highlights a need for better planning during the software testing process. Real-world testing ensures that from a security point of view, these problems can be avoided and every possibility has been identified and managed.

3) Mt Gox - 2014

in 2014, Bitcoin began to make the headlines as a new and innovative online payment network where traders who spend virtual coins over the internet. While the concept has been adopted heavily in some circles, the security of the network is still up in the air. 

One example of this occurred in February 2014. A Japanese-based Bitcoin exchange company called Mt Gox suddenly went out of business for unknown reasons. The business couldn't account for $474 million in Bitcoin and other customer investments.

Industry sources claim that the original software used by the company had a "transaction malleability" flaw which had been bleeding Bitcoin to online hackers. Bitcoin software is often open-source, meaning that many people had a hand in its creation and development. However, this just adds to the argument that before any software goes live, appropriate and adequate testing is required.

 

As the above examples highlight, software problems can occur in even the most established of institutions. From banks and airlines to start-ups, software is vulnerable and needs to be tested thoroughly by trained and professional testers.

TTC is able to provide tangible testing solutions and work alongside businesses to ensure the software is perfect by the time it gets to the target audience.