I’ve found keeping a log of blog posts extremely useful, especially when writing blogs and article of my own. I often refer back to previous articles that I’ve read, and its much easier to do this when I have a list of what I’ve read. Including in my lists are additional notes that really inspire me on future posts. I also get a lot of inspiration from social media discussions and it can be useful to know the source of some of my ideas when I’m writing. This is why I’ve decided to start including social media discussions in my lists.
Very rarely do I go off topic, but I have to talk about last weeks episode of Game of Thrones. What an amazing episode it was, so amazing that it has inspired 2 software testing blog posts. One was published last week. I’m hoping to get the other completed and published next week. Inspiration can come from the most unlikely of sources sometimes.
The night is dark and full of terrors – I think!
In this blog post, I discuss issues that some fans experienced while attempting to watch last weeks episode of Game of Thrones. I explain how this may have been caused by the show designers not thinking about the fans, and how they might be watching the episode. This leads to software testing, and why it is important to think about the end user when testing software. The application is being developed for the customer, and should be designed so the end-user can both use and get value from using the application.
Social Media Discussions
Is regression testing a process or a technique? – started by Mark Winteringham.
Not much is needed to explain this topic. The question says it all. My answer is that it is a process, or at least part of the overall testing process. Regression testing can be done in several different ways. The way it is done is a technique which can change from tester to tester, and team to team.
Prioritizing and setting up regression test suites
An interesting discussion started by Natasha Juneja that recently appeared on LinkedIn. She asks if we prioritise test cases, and how we separate them out into regression or smoke tests.
A new discussion started on The Club. This topic was started by Yunus Kursuncu who wanted to know if anyone does UX testing and what their experiences are.
Communication between Developers and Testers
This was a small statement that I posted on linkedin about how developers and testers have the same goal and should work together to achieve that goal. It appears that most are in agreement of this.
Blog Posts and Articles
Use the Rejected Defect Ratio to Improve Bug Reporting by Michael Stahl, Stickyminds
In this article, Michael Stahl looks at why bugs might be rejected. He also discusses the rejected defect ratio, and why it doesn’t need to be 0. Rejected bugs aren’t a bad thing. There can be both positive and negative reasons for bug rejection.
The bug is gone by offbeattesting
All too common issue where a bug is happening one moment, then cannot be reproduced the next. What should we do when this happens? Two things that this article looks at is the importance of speaking to developers so the tester can get a better understanding of the issue, and recognizing that intermittent bugs are still bugs.
Bug Severity vs Priority in testing with examples by Kirandeep Kaur, LambdaTest
There is a difference between how bad a defect is, and how soon it needs to be fixed. Examples are given for:
How to stamp out intermittent testing issues with periodic automation by Paul Grizzaffi, test beacon
By comparing intermittent issues to hunting for big foot, Paul Grizzaffi talks about how software with so many connections are bound to be prone to intermittent issues. Unfortunately we can’t test everything, but the more you look the more you see. Intermittent issues are more likely to be found if more tests are run, which is made more possible with test automation.
- High Severity, High Priority
- High Severity, Low Priority
- Low Severity, High Priority
- Low Severity, Low Priority
Agile Elitism – undoing the good by Paul Seaman, Beaglesays
Paul Seaman discusses his personal experiences of agile, including one where it works and one where it didn’t. Agile may not be interpreted at the same company. Just because one place doesn’t follow the same, or even the ‘correct’ interpretation doesn’t mean its failed. So long as it works for the company. It is important to experience agile, not just read about it in a book and follow that book to the letter.
Approaching your automation – with measurement awareness! by Omri Berkovich, QaBlog
In this article, Omri Berkovich gives a list of things that must be considered when starting out with test automation:
- Candidate test cases
- Where to apply automation
- Tool selection
Plan to secure internet of things with new law – BBC News
Going a more into security testing. With the rise of internet of things (IOT), more and more devices are now connected to the internet. This has opened them up to vulnerabilities. How easy could it be for hackers to take advantage of this. This includes a video showing how a hacker was able to hack into an interactive toy doll and change what she said. This really made me think of the talk by Fiona Charles at UKSTAR earlier this year, who talked about potential negative outcomes to technological advancement. With this in mind, all I can ask is “Why does a doll need to be connected to the internet?
Other blogs that share lists of test related articles
Feel free to recommend anything that you think is of interest.
Main image taken from http://www.publicdomainpictures.net