Software Bugs We Don’t Want to See Repeated in 2015 – Neotys Testing Roundup

1. Software Bugs We Don’t Want to See Repeated in 2015—or Ever Again

We love “Best Of” lists – in fact we published our own list of the top 10 things that broke the Internet in 2014. Here’s another good one we found.

Security breaches happen, from Target to Sony, but sometimes it’s not malicious hackers causing pain points for consumers, society, and companies. Occasionally, there are bugs in the software that create panic, displeasure, and financial strain. Here is a look at some of the more infamous software bugs in recent history that we hope don’t get repeated in 2015—or ever again.

See the list here.

2. How to Test and Validate Your Database Backup and Recovery?

As QA becomes a more integrated part of a DevOps culture, testers find themselves troubleshooting more than just code. A modern QA group’s responsibility extends throughout the software delivery process, and that has some interesting implications. For one, you have to test and validate production infrastructure to ensure it is operating efficiently.

We found this short refresher – an article that discusses verifying and testing your database backups. It explains concepts such as what, why and how – as well as methods to test the backup.

Hope it helps. Check out the article here.

3. Discussion: Automated Testing: What QA processes should be directed at validating test code?

Here’s an interesting question for test automation experts: what QA activity should be directed towards verifying that automated tests do in fact do what they say? Given that significant resources are put into creating automated tests, and that they serve a commercially valuable purpose, what review/ QA processes should, in your view, be directed at confirming that they work? Has anyone here found tests that appear to pass whilst not actually exercising the SUT in an epistemically valid way?

What are your thoughts? Join the conversation.

4. When IT Falters, So Does the Company

In the old days, when business technologies were initially being implemented to replace manual procedures, when computers went down—which they often did—the original manual procedures were there to save the day.

In today’s world, except for the most rudimentary tasks, such as processing credit cards, the option of implementing manual procedures is not feasible. The work volumes are too high, the workforce is no longer accustomed to performing manual workarounds, and very little, if any, time is spent creating or updating the types of manual procedures not seen since the 1970s.

This is a thought-provoking blog post that goes into depth on this subject. Read more here.

Leave a Reply

Your email address will not be published. Required fields are marked *