Fast Feedback Loops & Fun with Ruby
Half-day workshop - in English
Ruby is "a Programmer’s best friend", but it can be very useful for all roles including testers, designers and others.
Let’s use Ruby to get feedback—as well as getting the 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.
If this happens to you as well—and you already know some Ruby (or a similar language)—you're very welcome in this workshop, no matter whether you're a tester, designer or programmer.
If your tools can be started from the command line, chances are very good that you can use Ruby to automate running them.
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.
To get the most out of the workshop you should:
- Have some Ruby knowledge; you don't have to be an expert or anything like that.
- Be willing to help others and be helped by others.
- Bring a notebook (or tablet) with an internet connection & Ruby installed. If you're using RVM, rbenv or chruby or similar, that's cool.
- OS X, BSD; Linux & friends should all be fine, Windows may be a bit problematic.
Primarily for: Developers, Tester/test leads, Architects, Others
Participant requirements: A notebook with a working Ruby installation (see abstract above). As long as it's unix-based, that should be fine, Windows may be a bit tricky and require attendees, to do more work upfront in preparing for the workshop or pair with someone who brought a unix-based notebook.