Here’s a short reminder that I’ll be speaking at the Agile Testing Days 2016 this December. As the banner says: If you’re planning to attend the conference, ask me for a discount (it’s a coupon code) and I’ll be happy to send it out.
The opening session of the Agile Testing Days 2015 was Western-themed and Janet Gregory and Lisa Crispin asked the audience to watch for gold nuggets at the conference — particularly valuable information or other things we would take home. I (actually my alter ego Super Agile Person) was invited to present my suggests at the ending session. So these are the nuggets I found at the conference:
I got a Calgary Stampede hat from Lisa and Janet. Thank you so much!It’s great, it fits and it even has inner values printed on the inside:
Commitment to Community
Pride of Place
The first two of them are particularly applicable in all communities.
In their opening keynote Alex Schladebeck (violin) and Huib Schoots (trombone) connected music to testing and played music too. They even handed out a large number of kazoos to the audience to play along with them!
I find the connection they drew fascinating, since other presentations I attended this year presented connections between testing and other activities. Two examples from FullStackFest are Ernie Miller‘s talk “How to Build a Skyscraper” and Lauren Scott‘s presentation “Shall I Compare Thee to a Line of Code?“.
I’m thinking about other connections, but that’s another blog post.
Many people use templates to write user stories or charters for exploratory testing sessions. A widely used user story template is this:
As a <role>;
I want <feature>,
so that <benefit>
While these templates can be very helpful to start, they are also somewhat limiting — and can lead to outcomes like ‘As the product owner I want feature X, so that feature X can be used’. This is not — repeat not — how the template is used well.
While templates can be worthwhile to get started with using user stories (for example), they can become too constraining as a team becomes more proficient in using them.
In that case, I suggest to use the term Free Style User Stories and Karen Greaves already helped me spreading the word:
At the “London Tester Gathering Workshops 2015” (also see #LTGWorkshops on Twitter) I offer a workshop “Fast Feedback Loops & Fun with Ruby”. For this, I wanted to give attendees a handout, to make applying the stuff covered easier and it was planned to be a list of brief recipes.
Suffice to say that the handout grew (and it’s entirely possible that this is ‘feature creep’ in action). In fact, it grew to the point that I decided to turn it into an ebook. The book is not done yet, there’s some copy editing to do.
My workshop at the London Tester Gathering Workshops 2015 is announced now! They’re offering an early bird rate until the 18th February, by the way. Find the abstract on the conference page or just read ahead. 🙂
Fast Feedback Loops & Fun with Ruby
Ruby is “a Programmer’s best friend”. Let’s use Ruby to get feedback – including getting feedback automatically – when working on projects. Whether it’s about transforming source code into test results (a.k.a. running automated tests) or generating image files from raw data, Ruby can be used to automate these tasks. Furthermore, it can also be used to automate actually running these tasks, e.g. upon saving a file to disk. Does that sound like a good idea? This session is for you.
I regularly bump into tasks that are…
tedious, if done manually
not done often enough, unless automated
still not done often enough, unless running them is automated, too.
In the workshop we’ll combine some Ruby tools to remedy this situation. In particular the workshop will cover:
Writing a simple Ruby program that does something useful, e.g. turn a markdown file into HTML
Wrapping that in a Rake task
Automate running the task
Knowing how to do this is useful, not only for projects using Ruby as their primary language, but can be handy in all projects.
What is expected:
Some Ruby knowledge; you don’t have to be an expert or anything like that.
A notebook (or tablet) with an internet connection & Ruby installed.
Cool if you’re using RVM, rbenv, chruby or similar
Mac OS X, BSD; Linux & friends are fine, Windows may be a bit problematic.