Confusing the user

Encountered when trying to do an online-checkin on the airberlin website:

Message in red says: „Online check-in is not possible at the moment, please try again later.“
Standard-message says: Check-in was successful, boarding card can now be printed.

Learning YouTube

Scrum in under 10 minutes

Source: http://shipsoftwareontime.com

Allgemein WWW

Stuff from my wall…

Today is my last working day at my current employer, and I´m removing my personal stuff from my office atm.
Some of the pictures/ things I´ve printed out and put on the wall, I feel are worth beeing kept, so here´s some stuff I look at quite often…

What are your printouts, you´ve put on the wall, to see it daily and being reminded or show others your attitude?

Testing YouTube

The INVEST Model for User Stories

INVEST is an abbreviation, describing the attributes, a user story should have: Independent, Negotiable, Valuable, Estimable, Small, Testable.

Via: Ralph’s Google Reader Recommendations

Programming Testing

Generate Unit Tests automatically (?)

For quite a while I´m thinking about a solution for following situation:
I have a lot of (old) scripts/ classes, which I created without unit tets (yes, shame on me, but by the time I´ve written them, I didn´t knew better, or didn´t had the time to do so, … the usual excuses).
Now I would like to add unit tests afterwards, to benefit from all the advantages they give to a programmer (find regression, give a safety net, etc.).

But I´m just too lazy to go all of my code and add unit test after unit test after unit test. Instead I would like to auto-generate them. At least the skeleton, like test classes & methods; so e.g. create a test method for every method used, create a test for every object that should be (not) accesible from the outside, etc.
I know that I will have to create the test logic by myself, so checking if a method returns the expected result (or not).

Before start coding a solution, I would like to know if there´s something existing like that already? If yes, I would appreciate any hints/ links/ articles etc., especially for Ruby, but Java and/ or C# would also be great.
Thx in advance!

Allgemein WWW

QuickLinks for December 2010

Here a quick list of articles I´ve read during the last month:


How to start regression testing from zero?

I´m thinking about how to solve the following task: You´re joining an (agile) team as a tester and you´re the one being responsible to do the (automated) regression testing. No structured regression tests have been done before, (nearly) no tests (test cases, automated test scripts, etc.) are existing. What you have are the user stories + acceptance criteria from previous sprints and the (user-)documentation as far as it exists. Maybe some other docs too, but that´s not the point.

So it is your task to start regression testing for the old functionality as well as doing the testing for the stuff that is under development at the moment. Since development is ongoing, you somehow need to split up your time between this two main tasks, but how?

I see two possibilities:

  1. Don´t care about the actual ongoing development, just start building up a regression test suite from the very beginning of the product on. Iterate over the user stories + acceptance criterias from the very beginning on, discuss with the product owner which ones are needed as basis for tests, and which ones may have become obsolete or changed.
    As soon as you´re reached the actual sprint, start to keep up your role as tester in the team by testing what is under development at the moment and updating the regression test suite.

    you learn about all the product´s feature from the very beginning
    you know about the „development history“ of the product
    regression test suite is build up as fast as possible

  2. Work as tester in the team by testing what is under development at the moment, but with reduced capacity. For the rest of the time work on builing up the regression tests. Do so until you´ve created all the regression tests up to the actual ongoing sprint.

    tester is available for testing actual stuff under being under development right on from the start
    tester is working as closely as he could(/should?) together with the team from the very beginning on.

Disadvantages for both proposals: Just invert the advantages of the other proposal. 😉

What should be done indepently from what solution is been chosen:

  • Regression tests should be automated, why and how is explained at other places, e.g. in the Agile Testing book or in the article Regression Testing with an Agile Mindset.
  • The task of adding regression test should be estimated in any case. It’s a reoccuring task and because of this it has value to estimate this task(s) from the very beginning on to learn how to do right estimations on this.

What do you think about this?
Did I miss a possibility or (dis)advantages of the explained possibilities?

Interesting article on Starting Test Automation for a Legacy Project which is imho closely related to what I have written: You can’t start test automation without having a clear concept on how to start regression testing. The article gives some good ideas on how to start for both.


Christmas goes Scrum

Nice story, unfortunately in german only: Weihnachten nach Scrum Manier

Via Thomas Nesges on Facebook


Kanban Christmas Story

Find a nice Kanban Christimas Story by Arne Roock and Henning Wolf at agile-it: Santa Claus Has Everything Wrapped Up Now.

Via @ipreuss on yammer

Allgemein WWW

Testing is like Heavy Metal

#testing is like heavy metal. Doom, death’n destruction, speed’n torture’n beautiful ladies dancing half naked around.no!last is imagination

Source: @teemuvesala