What You Want (And What I Offer): Client Oriented Testing
You and your team build software and you’re looking for someone who can help you with software testing. Preferably one who likes to share his knowledge and who’s ultimate goal is to make himself superfluous. The whole approach to testing depends on what kind of information you need to make your business decisions. Some questions are:
- Does the software meet given requirements/specifications?
- What are the risks of releasing (or not releasing) the software?
- How can we deploy continuously to our production system?
Depending on what exactly you need to know, the strategy, design and execution varies a LOT.
I help you to find the right questions for your business as well as set up a special tailored test approach for your product (or project).
As I wrote in “Testing And The Two Values of Software“
Also, I definitely want my clients, as well as their clients, to be happy with the software I help to develop, not only today […].
And I mean it. I do believe great software is possible.
I’m available for contracting, coaching and training.
Contact me at email@example.com.
To help you figure out how I can help you, here are some examples of my work — be sure to check out the blogposts, too.
Other Places on the Web
- Twitter: https://twitter.com/S_2K
- Polywork: https://polywork.com/seasidetesting
- GitHub: https://github.com/s2k
- Xing: https://www.xing.com/profile/Stephan_Kaemper/
- I’m an Agile Testing Fellow. As the web site of the fellowship explains, we are ‘a community of practitioners forging new frontiers in agile testing.’
- I’m A Champion in the Association For Software Testing.
Books and Contributions
I am the author of Fast Feedback Using Ruby:
I contributed to “More Agile Testing” (Lisa Crispin, Janet Gregory); see Chapter 23, “Testing and DevOps”.
This is a description of testing your infrastructure in a DevOps team.
I also contributed the German translation of ‘Quick Tools for Agile Testing‘ (‘Prinzipien für Agiles Testen – 10 Prinzipien für Agiles Testen’).
A Selection of Bug Reports
Bug reports are one work product of testers. Here are some links to bugs I reported:
- Product: FakeFS, a testing library to avoid using the real file system when testing (in Ruby)
Short description: A class method of the File class is not available when using FakeFS.
Bug Report: https://github.com/defunkt/fakefs/issues/224
- Product: RubyMine, a Ruby IDE
Short description: The code refactoring tool doesn’t accept an exclamation mark (‘!’) as the last character of a method name
Bug Report: http://youtrack.jetbrains.com/issue/RUBY-11106
- Product: RubyMine IDE / Cucumber
Short Description: For some test scenario descriptions (called scenario outlines) the reported test execution duration is too large.
Bug report: http://youtrack.jetbrains.com/issue/RUBY-11054
Remark: As you can see in the bug history, the ‘real’ bug was actually in Cucumber. That’s particularly fascinating, since I tested with cucumber only (i.e. running the scenario outside RubyMine) and didn’t find this.
- Product: The Euruko 2013 web site for ‘call for papers‘
Short description 1: The user can vote for talks by dragging them into a ‘Selected tasks’ list. This list couldn’t be displayed on some window sizes
Bug report 1: https://github.com/euruko2013/vestibule/issues/49
- Remark: Here you see how fast bug can be fixed, when volunteer testers and programmers cooperate and how much fun this can be.
Short description 2: The ‘drag & drop’ mechanism for voting on talks didn’t work on iPads
Bug report 2: https://github.com/euruko2013/vestibule/issues/50
- Product: OpenOffice (Writer)
Short description: With a large user-set page width, the left margin cannot be set to values larger than 99,99cm
Bug report: https://issues.apache.org/ooo/show_bug.cgi?id=122203
Remark: This bug report was provoked by an assignment in the great course ‘Black Box Software Testing – TestDesign‘, offered by the Association for Software Testing
Here’s some code I wrote:
It’s a Ruby gem that helps to detect whether or not criteria are met for at least or at most a given number of elements in a collection.
What People on exercism.io Say about the Feedback I Give
Same as text:
- Extraordinary feedback guided me by giving insights about paradigms that I could use
- He explains and guides you throughout the solutions’ iterations.
- Great advice to help me clean up what I thought was a good simple approach for an even better one.
- Great tip on reading about what the Max method can do. Helped to reduce the wording my code and make it simpler. I’m all for simpler!
- Quickly helped me get to the most terse (and readable) iteration.
- Great help by s2k, understand much more now!
- Clear and helpful comments, with good hints that helped me search for best methods.
- Very good feedback. Found an issue I didn’t see and provided a way to write the code better using one of Ruby’s own built in method.
- Really helpful comments and nice motivating tone
- Very good at helping students find an optimal solution with many constructive advices.
- Helpful critical feedback, kindly offered =)
If you prefer that, here’s a more classical view in form of a PDF file.