Bloggo back to the blog
Blog Spy: A Weekly Round-up From The Software Testing Blogosphere-->
Organizing an Agile Program: Part 2, Networks for Managing Agile Programs – Johanna Rothman
“In Organizing an Agile Program: Part 1, Introduction, I discussed the difference between hierarchies and networks. I used Scrum of Scrums as an example. It could be any organizing hierarchy. Remember, I like Scrum as a way to organize a project team’s work. I also like lean. I like XP. I like unbranded agile. I like anything that helps a team deliver features quickly and get feedback. I’m not religious about what any project team in the program uses.” Read part 2 of organizing an agile program here.
What does a technical exploratory test session look like? – Alan Richardson
“As part of “Technical Web Testing 101” I wanted to provide an example of what an exploratory test session with additional “Technical” focus might look like, at the same time demonstrating some of the capabilities of modern browsers whilst comparing them to proxy servers.” Read his post and watch the video here.
Communicating In a Test Description Language – Jeff Nyman
“A TDL (Test Description Language) is a constructed language that we use to describe, and thus specify, our requirements as tests. Or our tests as requirements, if you prefer. This is what allows testing to be a design activity. What makes a style of writing a TDL is adherence to a structuring element and a set of principles and patterns that are used to guide expression.” Read more on communicating in TDL here.
Android Test Automation Getting to grips with UI Automator – Julian Harty
“Over the last week I have spent about a day of effort getting to grips with the recently launched UIAutomator test automation framework for Android. It was launched with version 16 of Android (Android 4.1) however on 4.1 devices the framework doesn’t even have all the documented methods available. With version 17 of Android (Android 4.2), support has improved to the point that the examples can work acceptably.” Read more on his experience here.
Measuring Costs in Agile Delivery- Isaac Sacolick
“One of the questions I sometimes get on Agile Delivery is on computing actual costs. My colleagues and associates know that I advocate a two step process -estimating performed by leads on story stubs and sizing performed by the team on fully written stories.” Read more on Isaac’s tips to calculating the costs here.
Creative and Critical Thinking and Testing Part 1 – John Stevenson
“I was asked a question recently regarding which style of thinking to use when at different phases within testing, creative or critical and I started to think deeply about this. I quickly sketched a diagram to explain my thoughts to the person who posed the question. Then I thought I need to explain my thinking behind the diagram and started to write an explanation for each section of the diagram, this has turned into a rather long research paper and as such I thought I would share my finding on my blog.” Read more on John’s findings here.
A view into the future –using Scrum as teaching tool in high school (and prior?) – Rini van Solingen
“A few weeks ago I visited the Ashram College (high school) in Alphen a/d Rijn in The Netherlands. A friend pointed out that they have a teacher there, who is using Scrum with high school students. They call iteduScrum, but what’s in a name. The results are astonishing: student teams that are focused and motivated and that score a full point higher in their exams!” Read more here.
Software testing as a career – Alister Scott
Alister Soctt explains why he thinks Software testing can be the best career on the planet and the worst career on the planet. Read it here.
Do we need Software Testing and Test Automation ROI (Return over investment) calculations? – Anand Ramdeo & Komal
So what would be the ROI of reading this blogpost? It’s possible that you get an idea which helps you in your test automation effort or removes myths you may have about software testing or you find that you are in software testing field because of wrong reasons and you leave this field altogether.
There are many possibilities and all of them are difficult to quantify. In my opinion, it is difficult to quantify most of the activities we perform in our field – software testing. Read more here.
Severity vs. Priority – Michael Bolton
“Another day has dawned on Planet Earth, so another tester has used LinkedIn to ask about the difference between severity and priority. The reason the tester is asking is, probably, that there’s a development project, and there’s probably a bug tracking system, and it probably contains fields for both severity and priority (and probably as numbers). The tester has probably been told to fill in each field as part of his bug report; and the tester probably hasn’t been told specifically what the fields mean-or the tester is probably uncertain about how the numbers map to reality.” Read Michael’s post on severity vs priority here.