Another session was this Saturday, actually sessions (+WT and WTA). Its very good considering there were basically 6h for those willingly to join.

Even that I proposed the mission and got to play a little before the actual meeting, I think I got more knowledge about boundary testing and limits.

Everything will differ for a product and environment, but in this context I saw:

-a chat message goes through many locations. As we assumed (read the transcript) it will be probably be an Xml record at one point, then maybe a db record. Depending how the data stream is sent, we will probably have another set of limits.

-in testing limits we can actually do (without even trying)  security testing or Pen testing. So we should be also careful from the legal points of view.

-the boundary depends on the input. An alpha numeric char differs from another char. An example used were kanji (Japanese) chars (“Petteri Lyytinen: I tried to paste a text string that is 32768 kanji characters” ..”only showed the two dots”)

-anything too big is truncated (or should be truncated in some situations) and the process of truncation can be different in some cases, some unexpected

-some parts cannot be tested easily (or in the required time interval) like the history containing large messages

-tools help – this time we used one available, but in other cases tools need to be built up

Thanks to the participants:

Anna Baik, Ben Simo, David Vydra, Kristjan Uba, Lalitkumar Bhamare, Michael Larsen, Narasimha Reddy, Nitin Purswani, Petteri Lyytinen, Santhosh S Tuppad and Eusebiu Blindu (as host)

Over the past two weeks I hosted the European Chapter of WeekendTesting. The two missions were EWT39 – Optical Recognition and EWT40-Mission impossible.

The first question someone would ask is “Why?” Well, because a Weekend Testing session can provide several nice stuff that usually is not present (or not in the same way) as in a real job:

-you can just not participate (but this “free will” increases the chances of enjoying it and get something productive from it)

-usually there are simple applications to understand for all – and from this what remains is the way to develop an approach to test it

-its a way to spend time (maybe not the best, but not the worst)

-you can risk with stuff you cannot risk at work – like following the curiosity for an approach

-get others to know you (usually the after reports include mentions to your name – website links if you are easy to be found )

and many other stuff

Anyone is welcomed to participate and this is possible by:

- Looking on the WeekendTesting website, usually the announcements are here for the new sessions

- adding on Skype the username  “europetesters” in your list

- sending an email at europetesters@googlemail.com

- following @europetesters on twitter