Reading Recommendations # 24

Reading Recommendations - Adventures in QA

Summer is coming, I hope you enjoyed the hot days in Europe as well. Maybe you find a nice shady place to read the 24th issue of my software testing reading recommendations. This issue contains 7 blog posts and one podcast. There are topics dealing with: “What skills should we learn & teach to build quality in” from Lisa Crispin. Why Managers need to communicate to effectively. There is a interesting post about the 8 myths and facts about Internet of Things (IoT).

Google announced the call for paper for the GTAC, which is an awesome mobile test automation conference. One post has the topic defining your role as a tester from Markus Gärtner. Another post is describing the four most powerful tools of a video game tester. Maaret Pyhäjärvi is writing about her experience with test automation and how she failed with the used approach. And the last entry in this episode is the latest version of Testing in the Pub by Stephen Janaway and Dan Billing with the topic WTF are NFRs.

Enjoy reading the posts.

What skills should we learn & teach to build quality in? – Agile Testing with Lisa Crispin

Read more

People in Testing Q&A with Stephen Janaway

Stephen Janaway - Adventures in QAThis time in “People in Testing” I had the chance to interview Stephen Janaway, who is a well known expert in the mobile and e-commerce software testing world. Stephen has more than 15 years of experience and worked for companies like Nokia, Ericsson, Motorola and the Net-a-Porter Group.

In this interview Stephen will talk about his challenges he is currently facing, which test automation tool he is using, where he sees the software testing industry in the next years and the best bug he has ever found.

Daniel: Stephen, what is currently your biggest challenge at work?

Stephen: I’m working on a new social commerce platform. It’s a real greenfield project and a new direction for both the company and the team. And me. So it’s a very steep learning curve but a really enjoyable and challenging one. There’s a lot of testing to do and we’re trying to do things as sensibly as possible; employing both automation and good exploratory testing using the whole team.

Read more