Bloggo back to the blog
Blog Spy: A Weekly Round-up From The Software Testing Blogosphere-->
Rapid Software Testing – skilled software testing unleashed – Zeger van Hese
“The software testing profession looks like a steadily maturing profession from the outside. The reality, however, is that the field of software testing is torn between different “schools” of testing. You could see these schools as determined and persistent patterns of belief, speech and behaviour. This means that different people – all calling themselves “test professionals” – have vastly different ideas of what testing is all about. So what are the options for a tester on a quest for knowledge and self-improvement? What is a budding tester to do? I think there are valuable alternatives for people who are serious about becoming a world-class tester.” Read more here.
Creative and Critical Thinking and Testing Part 2 & Part 3
“The last blog post (part 1) looked at what critical and creative thinking was and which may be most useful during different stages of testing. This post will start by giving an overview of each stage and then look in depth at each of the stages.” Read part 2 here.
“The previous articles in this series have looked at what is critical and creative thinking anddefining the stages of testing. This article is the start of looking at each stage in detail and advising which may be the best type of thinking to apply at that stage as described in the diagram from the first article of this series.” Read part 3 here.
25 Mantras That Will Make You A Happier Tester – Colin Cherry
“In my experience there are many frustrations in the daily life of a Test team and this can lead to frustration and even stress. So, in order to make your day a little less traumatic post this list of mantras above your desk (or create your own version) and I guarantee your day will pass more harmoniously.” Read the 25 Mantras here.
Testing And The Two Values of Software – Stephan Kamper
“Sure enough: If your team’s software fails to provide value now (or in the near future), something’s gone badly wrong. You don’t like your software project to end up similar to this, right?” Read more here.
Principles for Agile Test Automation (2nd Edition) – Emily Bache
“I’ve previously written about Agile test automation principles, and since then I’ve had some interesting discussions with people that have led me to revise them in this article. In particular, Seb Rose wrote about his 6 principles of unit testing and pointed out some issues with mine. So this article is an update on the previous one, and I’m hoping this will spark further interesting discussions!” Read the article here.
What is an Agile Manager – Luis Goncalves
“In this post I want to talk about the role of an agile manager. From my experience, middle managers are the ones that suffer more with an agile transition, let me explain what I mean. When agile is introduced at companies, there are typically three “layers” that are affected at the company: development teams, middle management and top management.” Read more here.
Take Good Care of Given-When-Then in the BDD – Shashikant Jagtap
“Behaviour Driven Development a.k.a BDD enforces agile team to write human readable, executable specification. Gherkin is a very nice Domain specific Language which support human readable syntax in different languages. BDD is all about bridging communication gap so writing better feature file is a key to success in the BDD projects.” Read more here.
Requirements. The Reality Is… Mohinder Khosla
We recently published a video that was recorded at the 2012 EuroSTAR Conference during a 5 minute Soap-Box session. In the video Fiona Charles discusses ‘Requirements suck? Get over it!’ You can watch the video here.
Johan Zandhuis responded to this blog post with ‘Requirements suck? Get over it!’ … No, go get them!
Mohinder Khosla now gives his views on Requirements – The Reality Is…
Organizing an Agile Program, Part 3, Large Programs Demand Servant Leadership – Johanna Rothman
“In Organizing an Agile Program, Part 1, Introduction, I suggested you think about the communication paths of your programs. Instead of hierarchies, I suggested you think of networks of teams. In Organizing an Agile Program Part 2, Networks for Managing Agile Programs, I showed you how loosely connected networks might work. I explained how you need communities of practice. I brought in the idea of roadmaps, architecture, managing the backlog and status. Now, it’s time to discuss what happens with program management on large programs, programs of nine teams or more.” Read Part 3 here.