Bloggo back to the blog
Blog Spy Vol 20: 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.
Do We Have a War for Talent in Software? – Johanna Rothman
“I read this piece, The War for STEM Talent is a Lie. I agree. Until we do all of these things:
- Hire the people who are in their 40′s and 50′s. People who are older than 35 do know something.
- Hire the unemployed and train them
- Hire the people who are not in your general geographical area and provide some relocation assistance
- Train the people you have!
Then I don’t think we have a war for STEM talent.” Read more here.
Why You Need a Product Owner – Bob Gower
“You’re building a large-or even a small-complex system like Aa website, a piece of software, a product that mixes software and hardware, or a services organization made up of people.
And it’s natural for you to think of this as a construction process. After all you’re building something big right. And bringing a lot of people together to do the job.
But a complex system is nothing at all like a house (a house today in fact is nothing like a house but we won’t get into that now). And your factory is nothing at all like a construction site or an assembly line.” Read more here.
The Cost Of Certification And Professional Exlusion – Duncan Nisbet
“There’s been a fair amount of chatter recently regarding certifications & whether they’re good, bad or actually provide any value.
I’ve been looking at them from a different perspective – As a self employed Tester, if I can’t afford the certification & any related training costs then I am immediately excluded from roles at companies where the certification is mandatory.” Read more here.
Advancing collaboration – Lisa Crispin
“You know how some topic will come up, and suddenly you notice it’s coming up over and over in different contexts? Lately, for me, that topic has been collaboration among roles on software teams.
My own team practices a “Whole Team” approach to development, and we testers work closely with the developers on a daily basis.” Read more about how Lisa’s team collaborates here.
You need to schedule tasks to “waste time” as part of your regular work! – Joel Montvelisky
“Throughout the years I’ve had the luck of working with some pretty smart and interesting testers and programmers.
The reason I call these engineers “interesting” is because they constantly brought to the team all sorts of new stuff (technologies, methodologies, articles, tools, etc) that ended up making our work more effective and even more enjoyable.
This is one of the things I like most about PractiTest (the company I’m working in today). The team is aligned with the philosophy that experimenting with new stuff is not only fun; it is also the best way to improve our product, to fine-tune our methodology, and even to increase the effectiveness of our company.” Read more here.
Popular books for testers – Huib Schoots
“I love to read and I own many books on testing, software, management and other stuff that relates to my work.
But what should a tester read? On this blog I recommend several books in my great resources list. And what do other testers recommend? My curiosity kicked in and I sent out an email to my tester friends around the world.” Check out Huib’s list of recommended books here.
A new teams encounter with DET/TET as a framework for testing – Part 1-Context – Sigurdur Birgisson
“Over the last year I have been asked many times about how to implement DET/TET at a new company. Since most of my experiences have been within Jayway where the concept is accepted, I have not been able to answer that question in a good way. This is my story of implementing DET in a company which had not been using it before or very much any other formal testing.” Read more here.
Mindset of a Tester – Gareth Waterhouse
“In light of another flop at a major championship for an English national team (Under 21s European Championship), and reading an article on sports psychology and what sports professionals can do to be at the top of their game, it got me thinking what can a tester do to stay at the top of their game? What type of mindset is important for a tester?
I find that all too often, people in testing just glide through without trying to further themselves and improve themselves.
In the article above it highlights 6 ways that a sports professional can maximise their potential through the right mental attitude, I will take these and adapt them so that they can apply to a tester.” Read Gareth’s advice here.
A Values-Based Approach to Systemic Test Team Problems – Jeff Nyman
I was recently in a work environment where we had literally thousands and thousands of test cases that were stored in a tool called TestLink. A major problem was that there was very little impetus for the testers to ever really analyze all these tests or to ever question if TestLink was the most effective tool to be used. This was due in part to some members of management who, perhaps in fear of bruising egos or seeming too critical, basically said: “What we’ve done has worked.” When the testers heard that, they basically assumed: “Well, that means our testing has been good.” Eventually I came along and essentially argued that our test repository was a mess and that our tool of choice was not the most effective. Read about Jeff’s experience here.
Creating an effective defect report – Mike Meurs
It’s easy to monitor on defects, but when you start reaching your 1000th defect and you keep track of all kinds of data, you might start loosing control on what the actual quality of your application might look like. You start to lose overview on where the issues lie and what actions need to be taken to control product quality within delivery time. You drown in the graphs you need to present and in stead of reading your report yourself and making the correct conclusions, you’ll use your energy creating the shiny report that nobody reads. Read more here.