‘Documentation’ Archive

Rapid Test Preparation Martin Jansson 9 Comments

At many bigger companies where you have several teams working with the same test scope there is often a need to communicate how you intend to test something and what areas you intend to cover. It is common that you have a test plan and perhaps a test strategy, they usually do not go into […]

Creativity in The Testing Planet Rikard Edgren 2 Comments

I have written a small article for The Testing Planet about Testing & Creativity. (update: web article here) It contains the potato from this blog, but also some new content on “cheating”. Feel free to add comments here! I think creativity still is too little recognized as an important aspect of our work. We should […]

Review of properties in Kaner’s What is a Good Test Case? Rikard Edgren 5 Comments

One of Cem Kaner’s many classic writings is “What is a Good Test Case?” It is a very good article, well-spent time for anyone involved in software testing. But when writing about test ideas, I started to realize that the list of properties for good test cases isn’t perfect, for me. So it’s time for […]

Passion, self-education and testing Martin Jansson 4 Comments

I’ve recently finished James Bach’s book Secrets of a Buccaneer Scholar. I liked it, but I don’t agree with all of it. As a tester, I feel that it inspires me and gives me new ideas in my way of thinking and how I perceive learning, especially self-education. I fully agree with James on that […]

Kaner’s Gold Mine Martin Jansson 2 Comments

Cem Kaner has updated his set of publications. I’ve been reading his well written articles over the last ten years. Have a nice time digging in!

Who does the pinpointing? Martin Jansson 4 Comments

Jerry Weinberg has, in his book “Perfect Software and other illusions about testing”, expressed a very important observation, namely who is responsible for pinpointing the bug. The tester finds the bug, tries to reproduce it, then adds as much information that he/she has such as log files, configurations, test data and so on. When you estimate time for testing […]

New tool – WordFreq Martin Jansson 3 Comments

A disclaimer… I am no developer, but I have developed a tool. As I develop I have the mindset of a developer, not the tester. I have done lots of mistakes, intentionally not implemented good/needed things and considered what parts I can get away with in the first release. This tool might not seem big and […]

The Inquisitive Tester – Part II: Question the specs the test eye No Comments

Statements in specifications try to clarify and are inevitably an interpretation of what the author thinks need to be more specific. I.e., they try to be a more specific model than what existed before the spec. And “Essentially, all models are wrong, but some are useful” (http://en.wikiquote.org/wiki/George_E._P._Box). Every specification you encounter is persons’ interpretations, and  […]

Are we ashamed of software testing? (And who is willing to pay for it?) Henrik Emilsson 1 Comment

Imagine that you run a software consultant shop where you take on projects for customers. The projects cover such areas as new software development; implementations of IT systems; and web site development. Let’s say that you are about to create a offer for a new project to a customer. Do you dare to specify the […]

Growing test teams: Progress Martin Jansson 2 Comments

A lot of these ideas come from Peopleware by Tom DeMarco and Timothy Lister. As I see it, they realised it is easier to show things that will stop the growth instead of listing things that will actually create the team. Jelled teams are created when many of the factors have been eliminated that stop […]