Rob is asking testers to write up post it notes with why they like testing and send them to him – read more here.

So last night I spent about 45 minutes contemplating this question, and when I didn’t come up with anything useful I just went to see re-runs of Tourchwood…

But this morning I had one of those EUREKA moments, and all of a sudden every became clear once more.

I enjoy the interaction with all the project stakeholders, from customers and product owners and all the way to developers and project managers.  I like the fact that my job is to work real close with all of them and serve as a bridge that allows the project to get done correctly.

I also enjoy the hunt, and the adrenaline of the projects, etc.  But specifically about testing it is the pivotal role within the organization.

This means I can send my picture to Rob.  Now it’s your turn to think about it, write it down and send the picture to Rob too.
Why do you like Testing???

No related posts.

What we like most about the magazine is that it’s fresh, cool and different.  Starting from the large number of new names who published their articles and all the way to the fun stuff such as the tester cartoons by Andy Glover, the blogs and even the conversations that are included inside inside.

A lot of people worked hard to make it happen, from the authors who submitted the articles and the rest of the pieces, and all the way to Rosie and Rob who literally spent days and nights to get it published.

THANKS, YOU DID A GREAT JOB!

Now I can’t wait to see what will come out in the next edition…

Related posts:

1. Testing Experience Magazine – Second Edition

I had not played Sudoku until about a month ago when I was stuck in a boring meeting and the only thing left in my BlackBerry (after being done with mails) was the Games Menu.

By elimination, and since I had never played it before, I decided to give Sudoku a chance. I choose the MEDIUM LEVEL, after all I was only trying to understand how it worked, and bum!
I got hooked.

Putting aside the addictiveness of the game itself, there are some pretty good attributes to Sudoku that are fundamental to every tester out there.
Naming only a few:
- Analytical pattern recognition
- The ability to look at what is there, and concentrate on what is missing
- Focusing at a problem from multiple angles until you find the thing you were looking for
- Even how to handle sisyphic tasks that not always end in success

There are many games that can be used in order to evaluate and even develop your professional abilities as a tester.

For example, “Where’s Waldo?”
I remember playing this game as a kid. It’s all about developing your eye’s capacity to find a needle in a hay stack!

You can even play Texas Hold’em poker on the Internet.
Weighting your hand while you try to figure out your opponents’ chances based on the open cards on the table helps you to develop your analytic capacity to extrapolate (and take risks!!!) under pressure.

There are many more games that can help you and your team do a better job as testers.
Remember that testing doesn’t need to boring or monotonic all the time…

No related posts.

Back when I was growing up social life was simple.

You defined your friends as the bunch of kids you played ball with or climb on trees in the park in front of your house. To be social meant to sit in the table and carry a nice face-to-face conversation with someone. Your pals were the guys and galls you went out for a beer once a week (or twice a week on a good week!). And the biggest social challenge you faced was how to fill your ego with the positive energy needed in order to ask the girl you liked to go out on a date.

Be My Valentine Charlie Brown

But today, Oh-Boy!

Being social is practically a full-time job!!!  No wonder people don’t have time for much else these days.

We have blogs, tweeter, professional networks, professional forums, social networks, Linked-In, Plaxo, multiple email accounts, multiple messengers, and the list of important media channels goes on and on and on…

If you want to be socially up-to-date you need to spend at least a couple of hours a day just checking all the information updated in these places, not to mention adding some information of your own in order not to be a silent listener (we all remember the Reebok commercial – Because Life is not an Spectator Sport!)

So here I am part of this new reality where.

-  I have MANY friends (not colleagues but friends!) I’ve never meet and live in places I haven’t ever visited.  We talk about work challenges and help each other in tasks; we are even up to date on all sorts of personal events and milestones.

- I am part of a great project to launch a testing magazine online with people I haven’t ever meet.

- I communicate with my best childhood friend using the BBN (this is the BlackBerry Network, for all you iPhone users out there), sending information and picts daily back and forward, and realizing we haven’t actually talked in close to 2 months!

- I talk to my parents using mails and messenger, and foward you-tube links to my brother to remember about stuff we used to see and do (and fight!) when were growing up.

- I go to conferences where all of a sudden someone comes to me and says “Are you JMG from QAForums? Well, I am <add username here>, we have been interacting for years!”

- My computer literally drives me nuts with all the tweet-tweet sounds once every 15 seconds or so.

- And on top of that, people get mad at me because they sent me a fish and a hug on facebook and I didn’t correspond by buying them a virtual drink (or something like that I don’t really understand)

Here’s the truth, I feel I am drowning under a surge of social media!!!

This stuff is like water, the right quantity is good for you and necessary to live and prosper, but once you get too much of it you are in danger of drowning (too much of a good thing?)

So this week I took a small first correcting step to take charge of my life once again.
I deactivated my facebook account. To tell the truth I hadn’t logged into my account in close to a year so it didn’t really make a concrete difference, but it actually felt good…

After I did that I talked to a friend considered by many (including myself) as a great example of a Social Tester, and he made realize this may be a case of becoming a kind of “Anti-Social” tester.

You know what…?
He might be on to something, and I think I like that direction!

So here’s my early New Year’s resolution:
From now and until the end of January I will closely examine all the social media networks, communities, sites, etc I belong to.
I will make sure only to be part of the limited number of communities that provide me with value (and where I fell I can add value too), and I will do my best to manage these channels and not to let these channels manage me.

Hello, My name is Joel and I am an Anti-E-Social Tester…

No related posts.

Let’s start with the QA&Test conference in Bilbao, Spain.
One of the warmest conferences I’ve been as a presenter; in-spite of the rain and cold weather outside in the city, the sessions and the hallways were a great and warm place to meet fellow testers and exchange information and knowledge.

Guggenheim Museum in Bilbao

If you are up to the challenge and understand Spanish you are welcome to check this short interview they did of me (Mae, I was expecting you to cut the bad parts…)
In short, QA&Test is a truly recommended conference.

Then I got back to the office where we really turned up the heat on our development (& testing!) process in order to release PractiTest’s latest update that included the first version of our Jira integration.  By popular demand (of a large number of our users!) this was the first integration we created.
So for all you Jira fans out there, come and get it!!!

The third update is that I am starting to get involved in a very interesting test automation project taking place on a company where Agile is not only their newest fad, but where they are really leveraging this philosophy in order to change the way they develop (and test!) software.
So, expect to read some stuff coming from that arena soon.

And finally the invitation.

I am honored to have being invited to provide a Mini-Track session on the upcoming Israel-SIGiST meeting taking place on November 24th.

The name of my session is “A bug is only a bug, right?  Wrong!” and I promise to provide some food for thought around the things we do and some we don’t with one of the main outputs of our work as testers, our bugs.

Related posts:

1. Testing Intelligence in QA&Test ’09 – Bilbao

We arrived in the US on a flight from Costa Rica on a Sunday evening, I am guessing that my flight had something like 120 or 130 passengers and crew.  After disembarking we proceeded to the immigration section and right away noticed something was wrong.  There was a line of about 1,000 passengers; but while all the immigration officers were in their places no one was interviewing passengers, all were talking among themselves or simply resting and staring at the sealing.

When we got to the line we understood the problem as the person in charge of managing the line came to us and said: “Welcome to the US, we are sorry but the system is down“, then after seeing the frustration in our eyes she said this had never happened before and she couldn’t tell us how long we would need to wait.

Here I need to say that my wife is a genius!! Her maternal instincts immediately kicked-in as she told the line manager that we were traveling with 2 small children and had a 12-hour connection in less than 90 minutes…  this gave us direct access to the beginning of the line (and generated angry looks from many people standing in front of us).

When I got closer to the boots I realized how not-out-of-the-ordinary the immigrations computer system was, and how I had already seen situations like this happen to my clients and even to me as a customer.  From the conversations between the officers I understood that the system had fallen some 15 minutes before we arrived, the computers had frozen and they were not able to process any visitors.

During the next 20 minutes I saw how an “IT related officer” (on Sunday night you won’t expect a real IT geek to be around, right?) tried to troubleshoot the problem.  He went through the rest of the officers’ boots and asked them to do different operations based on a printed guide he had with him.  Stuff like resetting the computer, trying to access via a secondary account, taking out stored laptops and trying to log into the system, nothing seemed to work and everyone remained standing there.

The gateway to “the land of opportunity” was right in front of us but it was being blocked by a simple computer that would not connect to a remote system and allow it to make sure neither me nor my family were a “Persona non grata” in the US.

Then, all of a sudden something magically positive happened; one of the officers was finally able to log into his computer and regain partial access to the system.  It took him twice the time to process each person, but 10 minutes later we were able to continue our journey home by stepping out of immigration, getting our bags, rechecking them to our flight to Israel, and reaching the gate running 5 minutes before the final boarding call.

I imagine that in due time the posts managed to get back on-line and eventually all the people in the line, that by the time we left already numbered a couple of thousand, got through the system (or not!).  But this certainly changed the plans and trips arrangements for many passengers, some of whom arrived late to their homes while others must have certainly missed their flights altogether.

This is just another example of how we are all dependent and controlled by Information Systems (in more ways than we care to accept), and how a flaw in one of them can turn our day (or trip!) into mayhem.  Nothing we can do, but learn our lesson well and make sure that as Testers we add “alternative system access and recovery” scenarios to our test plans, to make sure other people will not need to suffer due to the fact that we did not foresee out-of-the-ordinary scenarios that will eventually happen to our systems under test.

No related posts.

My presentation itself went pretty well (I think) and many people agreed with the TI approach, no surprises there.  But the real value for me came from the people who initially thought the method was not doable (or even realistic!) for their workplaces since it involved to many changes and education of their management on this new approach.

Reviewing the subject together with them I got to understand that the best approach for deploying TI on large organizations is to do it gradually and from within, based on a slowly-progressing plan that would allow the organization to learn and adapt to it, enhancing the chances for success in these environments.

The Testing Intelligence paper and the presentation I gave are posted on the CAST2009 site.
If you get to read them and have any comments, please make sure to send them to me.

I also wanted to talk about my CAST experience.
I have been in many conferences in the past (both as a presenter and an organizer) and so I can point to some stuff that really made a difference on the impact and the value I got from CAST. I invite the people organizing these types of conferences in the future to contact the CAST Team and try to learn from them.

1. Achieving real constructive criticism via facilitated sessions.
The methodology at CAST is that each session (from the largest keynote to the shortest presentation) are divided into 2 parts:
The frontal presentation – where the presenter talks about his subject.
and
The open season – where the audience asks questions, bring forward comments, and even refute the whole argument based on their experience and points of view.

The open season is made possible due to the active moderation of a “trained facilitator” who is constantly making sure the session is kept alive and on a positive and constructive note.

As a presenter, it is a bit scary at first.
Only after you understand that the audience doesn’t want to take you down but wants to help you out, can you participate from the interaction and even enjoy it.

2. Real eye-level interactions between all the participants (and I mean all the participants!!)
It doesn’t really matter if you are a junior tester or a published expert, it always felt right to approach a person and talk to him or to take part in an open discussion (with cups of coffee or bottles of beer!).

Some of the biggest names in the world of testing took part in the conference (Caner, Bach, Weinberg, etc) and at no time did you feel that any of them showed nothing but the most sincere sympathy (or at least respect!) for everyone else.
I don’t know if it was the blend of informal activities or simply the attitude of the organizers, but it was amazing.

3. The feeling of a peer-organized conference.
Again, this was a “feeling” more than something concrete, but at no time did you sensed any hidden agendas or sponsor oriented activities that made you feel someone was trying to sell something.

I don’t think I saw a single person in the conference that was not related in one way or another with the art of testing or at least teaching testing, and this made a whole lot of difference.
A conference from testers, by testers and to testers… what a refreshing idea

There were also the regular things you get from any “large” conference: a constant brainstorm of amazing ideas, camaraderie and genuine will to share and learn, and the chance to expand your circle of friends and colleagues.

One last thing to mention about this CAST was the fact that it was a relatively small conference, apparently affected by the “current economic crisis” that made an important number of people not to come to the conference.
I don’t know if this affected the conference itself, or if it actually helped to create an environment of a close and connected family of testing professionals that would not have been achieved by a group twice as big.

In any case I wanted to give my sincere thanks to the CAST Organization Committee who invited me to participate and allowed me to take part in the event.  Having had the experience of organizing similar events I can appreciate their work and performance.

I would start thanking by specific names but this will only make me leave out some people out, so as I already thanked each of you on the last day of the conference I wanted to thank you again as a group, for the great work and for the successful conference you allowed me to participate in.

I hope to see you all again in CAST2010!

Related posts:

1. In the CAST conference this week
2. I had a really good time presenting at the SIGiST mini-track last night
3. The Value of Peer Reviews (& why we don’t use it more!)

I will be talking tomorrow (Tuesday) about Testing Intelligence.
They even published and interview about my and the topic, so if you are not attending and want to read about it you can check it out here.

I will also post a summary of the comments I get during the presentation.

Wish me luck since I am little nervous about it

Related posts:

1. There really is a difference to CAST

I presented a session about QA Management Systems, and based on the questions asked there were in the room at least 10 to 15 Testers I’d like to interview next time I have an open position in my QA Team.

Where’s the problem, and I’ve seen this in Israel but I am guessing it is also an issue in other places.
Many testers looking for a job today do not have a College Degree in Computer Science and this makes their CV less valuable in the eyes of the average QA Team Leader and Manager. This problem becomes even more acute as a large number unemployed testers today have this degree as a line in their resume.

So here is my request to all the Team Leaders and Managers looking for testers:
STOP MAKING A CS Degree A REQUIREMENTS FOR A TESTER!!!

When are we going to finally realize that a Tester is not a type of Developer?

A tester needs to understand about programming, but we don’t need a formal degree on it (BTW, some of the most incredible programmers I know don’t hold a CS degree either!).

Instead of in-depth knowledge in programming languages, look for people who can understand the human language and can translate user requirements into tests that verify their real and complete needs.
Instead of looking for candidates with knowledge in development algorithms, look for people who are curious and organized by nature and don’t need an existing path to do their job efficiently.
Instead of someone who can inspect one line of code for hours at a time looking for a way to fix a bug, find the testers who will think “outside the box” and in a minute come up with 7 different scenarios to run on the new feature (and find the unimaginable bug!).

In short, understand what you look for in the person you want to hire, and then decide whether he needs a CS degree…

To the people without a CS degree looking for a Testing Job today (in Israel and maybe elsewhere), first of all understand that you are at an unfair disadvantage. Better to know this than to not understand the reason you are not getting as many interviews as the next guy.

Now, think about what you can do to compensate for this in your CV. I don’t have a magic formula, but you need to think about ways of getting around this issue and making your resume “look good” even without such a degree. One way of trying to do this is based on your personal and professional experience…

Lastly, realize that most of the good jobs are seldom published on Hiring Bulletin Boards, they are filled based on personal recommendations. So make sure all your friends, family and neighbors know that you are looking for a Job and are ready to recommend you next time someone asks for a good tester during an informal chat.

It’s in your hands to catch that Job before someone else does…

A closing comment:
If back when I started testing a CS degree would have been a prerequisite, I would not be writing this post since I have a BSc in Industrial Engineering…

No related posts.

Like a colleague here in Israel, Guy Arieli from AQUA, who came up with an idea to help Test Engineers looking for a Job who want to expand their theoretical knowledge in Testing and QA.
He organized a FREE 8 session course where the Engineers learn about stuff ranging from Freeware Automation Tools to the Basic of Mobile Application Testing, and cover important practical topics like preparing for Job Interview and the like (this is the site for the course in Hebrew).

Each session is imparted by a different person from the Industry, providing a lecture on his topic of expertise; and the lectures themselves take place in HP R&D’s Campus in Yehud.

This evening I will be talking about QAMS (QA Management Systems), hoping to communicate the importance and advantages of using this platform as an engine for Testing Intelligence. Obviously this is not much, but I hope it helps.

Kudos to Guy for the great initiative.

Related posts:

1. Great testers, not so great CVs…