Bloggo back to the blog
Blog Spy Vol 40: A Weekly Round-up From The Software Testing Blogosphere-->
A round up of some of the latest blog posts from the Software Testing Industry in the past week. If you would like to have your blog featured in our regular round-up, please email details and a link to the post to [email protected] or tweet us @esconfs.
How Many People Can You Manage as a Manager? – Johanna Rothman
“In my first management role, I “managed” one person. My managee didn’t need much management. He guided me into how to manage him more than I managed him. He saved me from making too many mistakes. It was great practice for me.
Later in my management career, I managed a “team” of 15 testers. They were not a team. They were a group. I’m not sure why my management insisted on referring to them as a team, but my managers did. My role was to match-make testers with projects.” Read more here.
In praise of ignorance – James Christie
“My EuroSTAR 2013 tutorial in Gothenburg was titled “Questioning auditors questioning testing”. Not surprisingly a recurring theme of the tutorial was risk. Do we really understand risk? How do we deal with it? These are important questions for both testers and auditors. I argued that both auditors and testers, in their different ways, have struggled to deal with risk. The failure of auditors contributed to the financial crash of 2007/8. The problems within the testing profession may have been less conspicuous, but they have had a significant impact on our ability to do an effective job.” Read more here.
Mapping Enough to Test – John Stevenson
“I have seen on far too many occasions, whilst working in testing, people spending months gathering together information and creating test plans to cover every single requirement, edge case, corner case. Some people see this as productive and important work, in the dim and distance past I did too. I have learnt a lot since then and now I personally do not think this is as important as people try to make it out to be.” Read more here.
Solving the real problem – Johan Jonasson
“This is a continuation of my post from back in August on the ISO/IEC/IEEE 29119 software testing standard in which I argued that the upcoming standard is a rather bad idea. This post is more about what I think we should do instead, to solve the problem the new ISO standard is failing to solve.” Read more here.
10 keys to a happy tester – Gareth Waterhouse
“I was thinking the other day over what makes a tester happy, and I thought I’d write down my findings, and share them with you, this isn’t necessarily what makes me happy, but more around what I think can make any tester a happy tester :)” Read more here.
How to test refactoring? – Jeroen Mengerink
“A fundamental part of the Agile methodology is refactoring: rewriting small sections of code to be functionally equivalent but of better quality. Don’t forget to test the refactoring! What do you test? The answer is simple: you test if the code really is functionally equivalent.” Read more here.
Software Testing: 21 Philosophical Questions – Colin Cherry
Colin shares 21 Philosophical Software Testing questions. Read them here.
Shipping Forecast – A Way To Get Things Done – Rob Lambert
“I was chatting to someone at EuroSTAR last week and we got talking about personal productivity. I shared with her my way of working using a concept I’ve been callingShipping Forecasts. It’s based around the simple premise that I will beshipping something (a project). It is called a forecast because no amount of planning is a guarantee, so I am forecasting about what is involved in shipping this project.” Read more here.
Activities in testing – a parallel from qualitative research – Alexandra Casapu
“I mentioned in the previous article that I would discuss more on the similarity of the phases in a qualitative research process and the phases of the testing activity.
So I continue here the parallel with the book – ‘Reliability and validity in qualitative research’, by Jerome Kirk and Marc L. Miller – and a more extended discussion on invention, discovery, interpretation and explanation…When I test a product, I go through a sequence of different activities that focus on different aspects of the testing process.” Read more here.
Software supply & demand – this time its Agile – Allan Kelly
“Carrying on from my previous posts applying the economists tools to thinking about software development (Supply & Demand in software development and Software supply over time). In this post I want to see what happens when we apply Agile…” Read more here.
Some Stuff I’ve Learned – Alan Page
“I picked up my Xbox One this morning – a special white console with “I made this!” engraved on it. The reviews started appearing last night, and for the post part, they’re quite positive (and I’m not surprised by the drawbacks listed in the reviews I’ve read so far). Now that this project is officially behind me – and before I figure out what’s next, I have some backlog blog posts to share.” Read more here.
Mind Maps and Automation – Karina Clokie
I’ve written in the past about the risk of relying solely on automated checking in release decisions. On a recent project I had great success in changing how the automated test results were used by including mind maps in the reports generated. Read more here.
Next time will be better – Amy Phillips
“Sometimes you don’t manage to do your best testing. Even as you frantically try to test more, to test better, you know that on this occasion you’re not going to walk away feeling like you did a great job. This was me last week. We were facing down an exciting deadline. Time was short. I had started on the back foot by missing the earliest project conversations.” Read more here.