Archive for category FitNesse

Stuart's introductions to Fitnesse, FitNesse Series (Part 2)


Writing the Fitnesse posts turned to be harder than I thought.
I do have a bit of tests ready for the triangle case, but not enough text to make an interesting post. As I’m not using Fitnesse in my day-to-day work, it makes it harder to bring cool insights or to explore on the framework.

But I just discovered someone who not only uses Fitnesse at work, but also writes articles about Fitnesse that give the Fitnese feeling:

Read the rest of this entry »

The Triangle problem as a starting point – FitNesse Series (Part 1)

  • Which came first, the chicken or the egg? And after all, why would any of them cross the road?
    That question is as old as time.
  • How would you test a program which can return the type of a triangle based on the side widths?
    That question is as old as me.

The Art of Software Testing cover imageIn 1979 (yes, I am that young 😉), Glenford J. Myers wrote what was to be the first classic book on Software Testing.
Called “The Art of Software Testing“, this book is very old, and written with old software in mind – most technologies and methodologies existing today were not dreamed of back then.
Well, it turns out the principles of software – from writing it to testing it – are still pretty much the same. Software is still written on sort of punchcards, the punchcards just got more complex and flexible… The book content is surprisingly relevant for today’s testers – so much, that it was updated only once in almost 30 years.
If you haven’t, read the book. Unfortunately, I have read it only partially meanwhile.

Maybe the most known contribution of Mr. Glenford in this book is the testing self-assessment challenge in the introduction.

Read the rest of this entry »

FitNesse Series in Testing Thoughts (Part 0)

Do you FitNesse?

I’ll (as soon as I get to do a lot of things I want to get done) post some impressions and examples on FitNesse, the cool tool for cool testers.

What I plan to do:

  1. Install and set a FitNesse setup;
  2. Make a simple standard easy program – the System Under Test!
  3. Start testing and making the program better with FitNesse.
  4. And 🙂 all this, with screenshot goodness!

When will that be?

  • Ouch. 🙁 It may take a long time. Let’s talk about this again on July…

Meanwhile: “FitNesse is designed to support acceptance testing rather than unit testing in that it facilitates detailed readable description of system function”. More information can be read in FitNesse’s website.