All posts by Mindful tester

No violence intended

A few weeks ago I talked about a locker problem with a woman of my sport school.
“I put my stuff in locker 8, but the door came loose.”
She smiled:
“Thank you for reporting. We’ll pick this and ..”

“then I moved all my stuff to locker 6.”, I continued at the same pace.
The woman halted. Wrinkles of concern appeared on her face.
“I could not close the door, because there was no current. Then I moved all my stuff to locker 4.”

I waited for a moment.
The woman could not wait any longer:
“What went wrong this time?”
“This one was all right.”
The apologising smile was back on full strength.
I got another set of apologies and a promise to fix.

Incoming heading

What about the rest?
It is not my purpose to leave a trail of bug reports behind. I just noticed something and I shared this with someone who was really interested.

I did not use any violence to break the door off. The hinges had been clicked to the locker. They just unclicked and the woman rememberedthis within milliseconds. I was also Non Violent. I used an element of Non Violent Communication.

What I did, was to tell my observation in an objective way. I did not use any upsetting adjectives like stupid or dumb. It was just a door.

I did not have to use the other parts of model, the feeling the need, and the request. The woman had enough information to fix.

In my previous blog post I already mentioned Non Violent Communication. I realised that I did not write enough about the non violent part. So this is my rebound blog post.

Feeling
After the observation I could tell about my feeling. “I felt annoyed. ”
Wait a sec. Annoyed reads very offensive. It is a feeling that I had at that moment. I am writing for myself. It is not targeted at a person. I just had an experience and I was annoyed about it.

I know there are people who would consider this as an attack. This should not be the case. That is the responsibility of the person who hears my story.

Need

That’s a proper heading.

I had a need for perfection. As a tester I am aware that this is not always possible. But the opening and closing of the lockers can easily be arranged. Common technology I would write.

My need is personal. Some people might whine about it or like it. That is their responsibility. I am the boss of my own feelings and needs. Of course you can help me to determine them, but I can tell which are appropriate. To me.

Request

My request would be like:
“Would you please repair lockers 8 and 6?”

Please notice “Please”. This is a request. It is also used in other languages: bitte, s’il vous plaît, or alstublieft. It actually means: if it pleases you. So it is completely fair to disregard this request.

I just stress it again: it is no order. I am a customer and not a boss. The action would help me, who asks for this action. My bad feeling will go away and my need be fulfilled. That is rather pleasing. For me.

My sport school could do nothing with my request. Depending on previous requests from my side I could stop my subscription.

So I am heading to …

The closing section
Once I read a tweet of some one. I interpreted that this person had enough of a situation. I tweeted:
” I would determine my need and make a reasonable request.”

In my next blog post I will write about being Non Violent in the testing field.

House rules for bug reports

Some people liked the TV serie about a doctor with a walking stick. This blog is about rules, which are applicable in a company or an office

“There is 1 rule: There are no rules.”
3rd movie about Mad Max

“This is not logical.”
Leonard Nimoy

Let me finish
The most dreaded part of the game: she or he will win for sure. Or worse we have to hang on for another hour. Of mental mockery. This is a sign of unbalanced game. A game you only play once. I am not writing about life here. This is not serious.

Some smart people developed some house rules to balance the game or to accelerate the game. Preferably both.

There is also some serious stuff to do.

One of the basic skills of a tester is to write decent bug reports. There are complete courses for them. I want to share some of my thoughts about them. Particular how house rules are applied to bug reports.

The trick for a good tester is to find the house rules for bug reports. Sometimes they are familiar. Let’s examine an imaginary situation.

  • Select movie Monsters Unlimited.
  • Select two for tickets.
  • Press Next.
  • Add Cola.
  • Set Cola to 1.
  • Add Lemonade.
  • Set Lemonade to 2

Actual situation:
The following message is shown: “You ordered too many drinks.”

Expected result:
It must be possible to order more than 1 drink per ticket. A warning should be shown.

That looks like a pretty example, how to describe a problem.

Let me determine some house rules:

  • Every button press is described.
  • It is completely repeatable.
  • The actions are described in an objective way. No hard feelings. Devoid of emotions.

This is logical.
Leonard Nimoy.

  • It describes what I would expect as a tester.

There are some serious drawbacks:

  • It is hard to read for a dev.
    One dev once gave up after reading my reports.
  • It took me time to write it well.
    You might have notice the tickets and drinks are set in different ways. And I am quite experienced.
  • A standard reaction is: “No user would ever do that.”
    Bug reports are not about proving the odds, but about telling the plausible.

So the trick is to modify or add house rules for bug reports. As a tester I have to make reports. As a dev someone else has to solve them.

It is time for Finding Marlin
“Finding Marlin you wrote?”
“Yep and I …”
“Don’t write any more.” [I just did.]
“It is about three fishes. Now the dad has been caught. Now his son and his blue thin friend whose name I always forget, go on a heroic journey to get dad back.”
What is your favourite sea dweller?”
“Dolphin..”
“So the dolphins are going to help.
And…”

“Thanks for your help.”
“Huh, I was just brainstorming about a movie spoiler. ”
“You just described a realistic situation, what people do in a particular situation.”
“Talking about fish?”
“Yes and showing how people can act in a natural way. ”
“I just happen to like movies.”
“And that’s what makes this talk completely plausible.”

Actually, Marlin stands for ‘Make a real life impression now’.

If I can tell a realistic user story, then devs are compelling to solve the problem. It is not something like this:
“As a cinema visitor I want to order my snacks and drinks before the visit, so I can save time.”
This is an abstraction.

It is about thoughts and needs. Let’s read a mind.
“In the movie Monster Unlimited there are too many monsters, so Mike and his blue furry friend have to move to the desert. That thought makes me thirsty. I need 2 lemonades for sure ”

Is this plausible? I think so.
Let’s ask the PO or Product Owner. Fine with you? So what are we waiting for?

Let’s tweak again
I do a small rewrite of my three drink bug report:

  • Order two tickets for Monsters Unlimited.
    [Hey. That is great. I can order my drinks in advance. Let me see]
  • Order 1 Cola.
    [Looking at a desert makes me thirsty, so I take an extra drink.]
  • Order 2 lemonades.

Actual result:
A message is shown, that at most 2 drinks can be ordered. [I need that drink. This is ridiculous.]

Expected result:

It must be possible to order more than 1 drink per ticket. A warning should be shown. [I take the consequences].

Let me extract some modified and new house rules:

  • The actions are written in a more natural way.
    This speeds up my reporting and it is more readable. I am not programming the programmer. I wouldn’t dare to.
  • Thoughts have been added, so people can identify themselves with the user.
  • Emotion has been added.
    This is a dangerous one. It is extremely helpful in the steps and can become harmful in the actual result. My thumb of ruie is, that it is allowed for a customer and in a few cases for a tester. A customer is not always a tester.

Are you in for a little experience? Have another read.

  • Order two tickets for Monsters Unlimited.
  • Order 1 Cola.
  • Order 2 lemonades.

Actual result:
A message is shown, that at most 2 drinks can be ordered. [This is ridiculous.]

Expected result:

It must be possible to order more than 1 drink per ticket. A warning should be shown.

“This is ridiculous,” sounds a lot harder than in the first rewrite, when only 1 thought has been added.

I will come back to the emotional part later and a few decimeters lower.

A more important question is: Why did I stop the presses? I mean the description of presses on a button or mouse.

This might be a lack of detail for some people.
“You ordered 1 cola and 2 lemonades. Right?”
“Yep.”
“So how did you do it?
Add 1 cola, add 1 lemonade and add 1 lemonade.
Or was it: add 2 colas, drop 1 cola, add 2 lemonades.
Or: add 1 cola, add 1 ginger ale. Drop 1 ginger ale, add 2 lemonades
I could even add some steps to go back, select Finding Marlin, order 2 drinks, change movie to Monsters unlimited, add third drink. But you wrote, that you did not do this. … Maybe.”

Sometimes programmers are great debriefers for testing.
What did you actually do? Why do you think this was a useful test? Did you also have a look at the other features? Did you also check the interaction with the other modules?

“They scare, because they care?”
That is not the appropriate way to write about devs. I do not have to fear, if I can answer their questions. And yeah I make mistakes like devs. Then I have to admit, that I was wrong.

Back to the example:

  • Order 1 Cola.
    [Looking at a desert makes me thirsty, so I take an extra drink.]
  • Order 2 lemonades.

Now I can make another house rule: take the shortest route.
Of course the devs have to agree. Then you have a new rule. In da house.

Can this lead to a discussion?
You bet.

“Did you test other combinations?”
“No, I was just exploring the web site.”
“Did you know you cannot order the lemonade in the winter?”
“No”
“So you better test it. It took me some time to program that.”
“Thanks for the information. I wonder how I can change the system time. Maybe you can help?”
“Well that is easy. You …”
I just leave these 2 techies alone. I have another interesting section coming up. In the meantime ..

is a scenic tour also plausible:

  • Order 3 donkeys.
  • Order 2 dragons.
  • Reduce the number of donkeys to 1.
  • Reduce the number of dragons to 1.

This is still the shortest route. Every step was needed.
You might call it Advanced Donkeys and Dragons. So long the troll stays away.

Lectori Ludum – Game for the reader
The game shown in the picture is the pocket version of the Hive. It is a 3 dimensional game and it has house rules.  And it is about bugs.
I like it’s complexity. In case you want to buy it, you could use this link.
End of commercial break.

Let me get emotional
I promised you to explain, why emotions are important. I already gave a small hint.

This is something I experienced.
I was in the hospital. The nurse behind the desk tried to formulate excuses to me:
“I did not give [your case] a high priority. You sounded completely in control. ”

This is a big disadvantage of being a tester. I had been programmed – I know: bad word choice. – to give an objective report, which put me in the middle of the line.

A bug report is a thing I not only make for work, but also in private life. If I don’t like something, then I want to get things fixed. So if I order a book and the book is damaged on arrival, I file a bug report. If the book seller does not provide a good service, I get angry. So why can I not show anger to get things fixed?

Do users of software have needs and feelings?
I think they do.
What about persona?

This is a description of customer with all her or his interesting characteristics. A good name can help a lot.

I do not have any experience with it. Personally I think it can be useful. No pun intended. I am a personal ally of the User experience or UX designer. That’s an intended pun.

Let’s start a thought experiment.
So we have the excited Kid, the bragging teenager, the unlimited cinema visitor, ….

Of course the excited kid will not handle the payment on a cinema web site, but she or he will definitely want to choose her or his own drink and snacks. “Dad, how can I order a Cola? It has already been chosen.”

A small side step.
For marketing people this is cool: can I sell packages to the kids?
For the regular movie visitor a limited collectible cup for the drink can be quite tempting. Gotta have them all.

Back to the Excited kid.
“Dad, did you really choose Finding Marlin?”
“Yes, I did. Just pick your drink and snack, dear.”
“What is a kid package?”
“I think it is a drink, a snack and maybe a toy in a box. Does the web site show some description?”
[A little silence]
“I can use a link. Yes you are right, dad. ”

[Another little silence]
“How can I get back on the page?”
“Push the back button.”
“It does not work.”
“Just close the tab.”
“It works.

Where is the page for the drinks and snacks? I cannot find it dad.”
“Let me have a look dear. That is strange I cannot find the tickets.
We have to start all over again.
O dear, all tickets have been sold out.”
This will start an outburst of emotions. In turn these form a good starting point for Non Violent Communication.

Last week while I was still assembling this blog post, I saw a tweet of Santosh asking about NVC. He had read a conversation between Jari and Lucian. And he couldn’t resist himself to “barge” in. I sent him a link to some basic  resources.

NVC stands for Non Violent Communication. This model uses 4 elements: observation, feeling, need, request. Luckily there is a cinema example available for use.

  • Observation
    The kid tried to figure out, what a kid package was. This led to a situation, that tickets were lost.
  • Feeling
    The kid is sad and the dad angry.
  • Need
    The kid has a need to share: to tell about the movie at school. The dad has a need for independence, that his kid can order her or his own drink and snack.
  • Request
    Would you please provide a way to show information about the kid package without losing the ordered tickets?

Browsing through these four elements makes the request reasonable. I am tempted enough to call it logical.

[Answer on, why his parents married]
“That was logical.”
Leonard Nimoy [TV serie]

By the way it took me a while to determine the need of the angry dad on https://www.cnvc.org/Training/needs-inventory. A need is personal. The basic thing is to describe the point of the view of the user. As an observer I have to be very careful to fill in the need of the user. It is not possible to read one’s mnd, but it is possible to ask about someone’s need.

Now I am quite close to the heart of the bug report. If someone asks to solve a bug report, then it is easy to program the expected result. If I test something, it is easy to check only for the expected result. And of course I can test all the other impacted functions and data, but does it really solve the problem?

Let’s have another look at the kid package problem.
A programmer could program the interaction as follows:

  • if the mouse is on the kid package, a small message will be shown containing the description of the package.
  • The message will disappear, if the mouse is moved.

As a tester I can easily determine, that the impact on the data and features is minimal. So it looks easy to test.

Well. There is a huge problem lurking there.

Let’s take a closer look
“So I have 2 tickets for Finding Marlin, 1 cola, and 1 carrot.”
“A carrot?”
“What’s up, doc?

So I go to the ticket counter and get tickets, the package, the drink and the veggie.”
“No, you only get the tickets. The rest you have to collect in the shop.”
“Why?”
“There is no place for all the snacks and drinks.”
“Sounds fair to me.”

“If I enter the shop I pick up my order and continue to the movie.”
“You actually have to collect all your ordered stuff yourself.”
“Why?”
“Just imagine a cola standing there for a few hours. It might have less bubbles and is warmer. Now think about ice creams. Or your carrot’s waiting days for a nibble.”
“You’ve got a point.”

“But where does it state that I have to collect all the stuff?”
“It is on the voucher.”
“Which voucher?”
“The one you get at the ticket counter.”
“Okay. Can you please show me 1?”
“Sure. Here’s one.”
“Hm that is small font.
That means I still have to be 10 minutes earlier to collect my order.”
“Uhuh.”

“So I collected.my order, I show my voucher and see the movie.”
“Yes, you just go to the counters to claim the voucher.”
“Wait. You said counters. But I do not have to pay again.”
“The counters have a scanner for the vouchers. There are so many orders, that there is no standard voucher.”
“Okay, let me summarise again.”
“Collect order, go to the counters, show voucher and see movie.”
“You’ve got it.”

“So I go with my voucher to the voucher queue.”
“There is no voucher queue.”
“Wait a minute. I have to get in the same queue like the other people.”
“Yes.”

“But there are no real benefits to the service. I only pay in advance.”
“Yes, but I like the idea of a special voucher counter.”

“The user story was:
‘As a cinema visitor I want to order my snacks and drinks before the visit, so I can save time.’
If I look for a need, i would say the need for ease. Within minutes I should get everything: just show the tickets and collect everything.

What about this?
How much time does it take to collect the order for a customer?”
“3 minutes.”
“So if I couple the GPS location of the customer to the order, then it is easy to collect the order. What about that?
Faster service and happier customers. Just make them smile.

And I could continue writing about what to do with the money in case if the customer does not show up. Or the customer changes his mind over the snack. Every solution should be focused on the need for ease.

Let me speed up the reporting
Navigation can be compressed using arrows. E.g. Menu => New.
If too many arrows are used, then the user experience should be improved.

It is possible to save time by adding bug descriptions in the comments instead of linking new bug reports to the report. If the devs can keep up with your pace of reporting, this saves lots of time. In one project I had a supplier, who had no overview and was slow. Then separate bug reports were extremely handy.

During my first year in an agile team
“I found a bug.
Do I have to report it?”
“You can talk about it?”
“So I do not have to write it.”, I wondered.
“We are talking.”, my scrum master answered with a smile.

Let me think
Post Ludum [After the game]
A continuing thought from me: are there other house rules to break? For better quality of life and work.

Why am I now thinking about retrospectives? It must be a flash of insight. I just wrote one : )

 

 

 

 

 

 

Let me write
I thank you for that.

Let me talk
I wanted to write a small blog post about bug reports and it almost turned into a talk. Too many stories in my head. So …

my proposals for talks for test conferences will be sent in the following months.

Let me thank you.
Thanks for reading. Real thanks again.

daD Talk

One of the things I wanted to develop is critical thinking. Not only by myself, but also by my kids themselves. The led to a rather unpleasant start of one of those dad kid conversations.

There was no way back: a subject I tried to delay for a few years:
computer security.

The complaint about a program was packaged as a request:
“I want to have a computer, which can execute [dangerous module] programs without using [dangerous module].”

I exhaled. My kid had absorbed the information and realised that the use could have a severe consequence for the computer. No more computer time. On the other hand the disadvantages were too big to forget about it.

I tried to find a solution, but I could not find one. If a program can change things on a computer, then it can do bad things.

While blogging I realised I was wrong. There was a work around.
There are programs, which can do same things like the original program, but they are built differently. They are called emulators. Some gamers like to play low resolution games on emulators of very old operating systems.
Wow, that’s my kid.

It’s hammer time
“If you have a hammer, then you can use it to break a window. But that’s not right.”
My kid nodded.
“So I program the hammer, so it cannot be used for a window glass. Then I can go to a door and use it to break a lock. I can program it not to break a lock. Then I can use it for a window frame.”

It would be easier to tell the hammer it could only be used on wood. This looks brown and it has grains. But it could be changed, so that everything looks like wood.”
I made a wide gesture with my arm pointing to different objects in the room.

“But I could change the picture. All objects would look like wood. That is not a good idea, so I store the picture in a book. But the picture in the book can still be changed.

Then I could place a lock on it. But the lock could be picked. I could place a better lock on it, but then the whole book could be replaced by another book.

And that’s why it is so difficult to secure things.”

Another unpleasant guest
My kid had seen a cool app. And it should be installed absolutely. So I did my dad thing:  looking at the permissions, which I would grant to the app. It could handle my files. It was just a game and why should game have a peek at my files? Time for the bad news.

So I told my kid, that the app would access files on the phone. The reply was to buy a phone just for games. Then I told that after a while the phone would be also used for other purposes like making pictures. “You don’t want your pictures in someone else’s hands.” There was a lack of nod.

I needed another way to tell the warning. A visual one.
“Suppose someone comes in. He looks television for the whole evening. And he eats the whole fridge empty.

If you protest, he will say:
“You said I could come in.”

The next evening he comes back. He takes the table and the sofa out of the house.

If you protest, he will say:
“You said I could come in.”

Delegate report about CITCON 2017 Amsterdam

“We did it already 14 times.”
Jeff paused for a moment,  “and this one was amazing.”
He was quite modest.

Gotta attend this 1
A few months ago a speaker told about his experiences at a conference. He had difficulties to make contact. One of the responses intrigued me. Mohinder Khosla mentioned CITCON in Amsterdam.

For a Dutchman this was interesting. The price was also reasonable 0 Euro with a modest request to cover the costs. But how could I determine whether the price was right? Among the participants I noticed Gojko and Cirilo. Wow. Then I read a recommendation of @testobsessed and I was sold. I mean the ticket.

Not bad for a conference with a marketing budget of 0 Euro.

Evening 1
Before I want to describe, what happened, I have a small warning. This post will focus on the process and not on the content. The reason I chose to is simple: people came there to share information and difficult situations. So reader beware.
Now it is my task to draw you in the atmosphere of CITCON 2017 Amsterdam.

The first day I used public traffic to go to the venue. It was hosted by Xebia. This office had all the elements to affect people’s mood. There was a standard meeting room with glass walls, a comfy corner including sofas and game computer. Did I mention the TV? There were rooms where I could see concrete shining through.

Evening 1 started awkward. I only knew one participant and he was not present, so I talked with new people. The talks were friendly with a formal undertone. Really polite. Just probing around.

Jeff and P.J. started the conference in a room with more than 100 seated people. They casually introduced the format. Asked for feedback (“5 stars is good.”). And let all participants introduce themselves and telling about things they were excited about or personal struggles. Those small stories let me connect to the people telling them.

The subject proposal session was described. At the moment everyone felt at ease P.J. and Jeff told, that they would take a step back. They would only help in case of problems. It was “your conference”. This lead to an extension of the Q&A. After the last question the organizers withdrew from the flip boards. It was up to us, the delegates.

After the warming up the real stuff started people were requested to pick a subject and clarify it to the audience. A queue formed in the room. People with posts its interested in solutions or volunteering to share information.

I watched the process for a half hour and I noticed the time. Time to send text message to my family, that I would come home later.
I really liked the way, how the subjects were presented. The question part was really clarifying. Participants tried to understand the content. The atmosphere had changed: it was warm and people were supportive.

Let me give an example. I proposed a session to share information about blogging. For me it is a way to clarify my thoughts and reflect. I was questioned about it:
“Why do you call it ‘Blogging as a service’”?
“I needed a title … and it is a service to the Community and outside the Community.”
BTW there was also a session proposed “What’s in it for me?” It was listed In the final program.

After the subject proposals I voted and went home. Afterwards I heard from a fellow Dutchman, that he was requested to compose the program. He kindly declined. He had already arranged the venue. This was a reasonable excuse.

Morning 1
The next morning I entered the office, where I had a small chat with Pati about conferences and IT. I skipped my second breakfast and collected a good coffee. There was a friendly buzz in the air.

I went to the program and browsed through the stickies on the flip boards. My session about blogging was accepted. Yay. Then the bad news sank in: there were too many interesting sessions at the same time. That happened to me years ago.

I arrived early for the first session. I remembered that several stickies or subjects were combined. The room was quite big for the small group. I moved my chair to the middle of the room for better interaction.

The first session was about testing and I tried to participate as good as possible. I had to watch my politeness, but I had no time. The subject was too interesting. I bent slightly forward and started contributing. I was in business mode: polite and helpful.
The day before the code of conduct was explicitly mentioned. Proper use of language was also checked :
“Can I use the F word here?”

For the second session I had to find the stairs. Glass walls wrre exceptionally handy in this particular case.

The previous session was still in full swing. I put me in the background, while observing the room. Sofas. These are great: It is difficult to maintain a neutral position. So I had an extra indicator for inclusiveness.

So I was in my session about blogging. And someone else. Okay time to start the Q & A. There were good questions. I got other questions than expected. Those made me think and reflect on my actions.

After a while other people joined. They had used the Law of Two Feet. If delegates were not interested in their session, they were allowed and encouraged to change the session. For my session it was welcome.

Lunch 1
During the lunch people were still having sessions. One session was about strange effects of particular Unicode on programs. A bit too tech for me.

You might have noticed that I changed the category to ‘Techies conferring’. My first thought was, that CITCON was about testing, until I read the description. It was about integration and testing. Other technical people would also be present.

During the lunch I joined a conversation about 3,000 pipelines. This was another world for me. So I had to drop my idea of an extremely small set of pipelines. There can be more than 1.

In a later session “mister G” had a good suggestion to improve builds. Suppose you have suppliers who are only focused on their own software. “Just let them provide tests to each other they can use in their build. If the build breaks they have something to talk.”
G thanks.

Writing about the afternoon let’s switch sections.

Afternoon 1
After the section switch I try to stay of content, but that is difficult.
One participant told a story about switching lines in code in order to cause bad unit test results. If the unit test did give an OK, there was likely a bug in the unit test.

I also saw some really awful Gherkin to describe actions instead of abstractions. Gherkin is good for testing of flows. For tabular stuff FIT of Fitnesse are the tools to use. And Concordia is another good option for the remaining option. Thanks Gojko.

For one of the final parallel sessions people were requested to bring real life testing problems. I joined this session. The facilitator did a good job to clarify the problem. A lot of whys and whats. I thought I could handle a lot of testing problems, but these were really hard to solve.

O yeah. Back to the process. I went to a big meeting table and met someone else. After some small talk we decided to start. About …
I volunteered to take a picture of the stickies. My hand went to my pocket and stopped. The location had been changed. I had been warned. So I warned the other and up we joined the session in progress about Gherkin. You might have read about it. Some centimeters higher.

After the session everyone was gathered in a room to share their AHA moments. There were a lot. I saw people who showed emotions. I saw people ready to take action when they would be back in the office.

People referenced to the ‘Gentle punch in your face’ session with Jeff. Other people had some great conversations. Outside in the sun. Hopefully a dev snd a tester. The truce is out there.

Evening 2
With more than an hour travel time and past my dinner time I had to find some place to eat. “It always works out.” Jeff reassured the people. Indeed a big group assembled on a terrace enjoying snacks, French fries, and burgers. They even had veggie ones.

I talked with other testers, who knew about context driven testing and cynefin. I don’t meet these testers very often.

There was a friendly guy with a nice sweater with a known software supplier on it. That made me curious:
“How did you get that sweater?”
“I work there.”
“I use your software.”
“Me too.” another techie joined in.

I ended in a group of Finnish guys. Talking about things. Things different from IT and work.

Thanks P.J. and Jeff for the conferring.

Pizza dough though

One of my kids read the recipe.
“Now we need salt. So I take the Baker’s Salt.”
And I had to switch gears: Baker’s Salt?!

For a starter …
On my days at home my wife hands all the cooking stuff over to me and I have to figure how to cook, grill, or bake. In my family weekend starts on Wednesday. My wife and I puzzle about the meals.
One of the no brainer recipes is pizza. I thought.

My wife was still collecting recipes. It basically meant, that I had to sift all kinds of papers. I already used the pizza dough recipe a few times, so I could tell the basic characteristics: white paper with a eightsome steps.

I browsed through the recipe folder: nothing.
I opened the Baking Bible: niente.
My kid was thinking all along the way.
“Let me have a look at the folder.”
Again: nope.
Then I remembered a book written by a national known baker. My kid had enough information and retrieved the book with half centimeter stack of recipes: bingo.

The next course is …
Next step to the dough was machine assembly. I put the machine on a comfortable place and picked the K-beater. Yep, that thing in the picture.  I still remember my first impression of this part. there is a K in it. When my wife mentioned the K-beater …

All parts were fixed. Now I needed the ingredients. My kid helped me measure the water and the flour:
“We need to use the patent flour”.
I agreed.
I was proud to remember to put the water first into the bowl. My wife had stressed that several times.

Then Baker’s Salt had to be weighted. A special spoon with a built in scale was used for this purpose.
“That is little.” I heard.
Before I could help: “It was 0.3 gram.”
I heard nothing more, so the accuracy problem was handled.

Then I wanted to add the Baker’s Salt to the water and the flour. But my kid was determined: it had to be added later on. OK. But we still needed the yeast.

My kid picked a small plastic cap out of the drawer.
“The salt and the yeast must not be mixed.”
The cap was placed in the spoon and the scale was reset.. Then the yeast in the cap was measured and added. Oil was also added.

Then it was time for me to start mixing. After a minute the salt was added. The K-beater had a heavy time, so I switched it after a small consult with my kid. Imagine a dancing kitchen machine. Not funny. So I used a new part. It looked like the left hand (?) of Captain Hook.

After 18 minutes I got the dough out of the bowl. My kid made a circle in the air with two hands:
“Mom always does this.”
“Can you show it again?”
The movement was a few times repeated. So I gently moved my thumbs over the ball of dough. My kid was not content. The ball was pcked out of my hands and placed on a kitchen cupboard. Then the ball was firmly cupped with two hands. The shape looked familiar to me. Nice touch.

I then let the dough swell.

For dessert …
“The pizza bottom is crispy.”, my wife remarked.
I bit and agreed.

Some people might have noticed that I did not use any computer related word. Except the bolded one. Let me continue.

My point is of course related to my profession. It was not about looking beyond the instructions neither about using knowledge in practice. This story is all about cooperation.

DUMB heuristic

During the Rapid Software Testing course James Bach advised to name things. If I cannot tell, what I am doing, my boss would think: “What the < beep > is he doing?”
So after the course I came up with the DUMB heuristic. This heuristic I use frequently during my testing.

Suppose my boss asks me how the testing goes. My answer could be: “I do uh my best.” A busy tester is always good, but if I am too busy things might go wrong. All my energy and brain power are focused on the work at hand. I forget to think. That’s DUMB.

When I figured out my heuristic, I had to find some smart explanation for this abbreviation. It became Do Uh My Best. Most heuristics are acronyms or lists of words. In turn every word is explained in detail. You know: turned upside down and shaken. But I just stick to the abbreviation.

Some readers have a good reason to ask. So hold on. The emphasis of the heuristic is on Uh. This is an alarm bell. Hesitation is a sign, that too much is going on in my head. I might forget to pay the deserved attention to the real problem.

This following discussion I had several times with my scrum master:
“I am writing test cases.”
“Why do you make test cases?
How often will the tests be executed? Who will maintain the test cases?”
So I was doing my best. And my scrum master got an Uh out of me.
He let me reflect on my work. What was I doing? And why?

Many test heuristics I know are acronyms. Some I do use. The S in SFDIPOT stands for Structure, how is the application under test built? So which components do I have to test? Etcetera.

If I apply this to DUMB then I would get things like: Do is the activity I am involved at that moment. It can be taking notes in my test charter or just thinking. Etc. Etc. The only thing I need on that moment is a short reminder to reflect on my work. DUMB. One syllable. Keep it sweet and short.

When do I use this heuristic? If there is a lot of work to do. When I have hours of straight testing ahead, I can go in my little cocoon and do something testy and something nice comes out. Tadah.

What about the focus and defocus stuff? Most of the time I use this when I got stuck. What can I do now? Let’s take a step back. Now I see the big picture. I figure out at a high level. Let me zoom in.

The point is, that doing my best is equal to doing stuff which is in front of my nose. I just pick it up and start running. Maybe I get it done today or this morning. Completely forgetting to ask for the reason. And that is DUMB. NOK?

When I was writing this blog, something hit me in the face. That was my imaginary hand palm. This so called heuristic is maybe already known under another name or in another way. Like a proverb.

And yes Madam within a few minutes the following proverbs came in my mind:
Eile mit Weile
Dépechez lentement
Easy does it

A day later followed by
Haastige spoed is zelden goed.

So why am I not using proverbs to keep my testing right? It is too long. Maybe a short heuristic could be useful.

“My scrum master would say something like Does it help?

This is really STUPID which stands for Some Thing …. I Do. UP are two words, so ….

Do I have to figure this out? WHY?”
“We Hear Yes.”

 

 

 

 

 

 

 

 

 

 

 

 

 

“GIRLS”
“Good In Real Life Software”

 

 

“GUYS”
“Graphic Userinterface You See”

 

 

“PLEASE”
“People Lik E A Software Errooor”

“CHEERS”
“Co Herent Entertaining Erroneous Random Synthesis”

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

So you are a mindful reader. Congrats. Here is the bonus.

Why did I not throw this blog post in the waste bin? People already thought about it and distilled their experiences to proverbs.

It is about my thought process. I do not want to stop thinking. Once in a while I discover that other people already have figured it out. Sometimes I find something new. But apart of discovery of new thingies it is about thinking thingies through. Getting better to verbalise my thoughts and explain them to you the reader.

That was what I forget a while ago. Thanks for the attention.

Optional reading Also Known As scientific stuff for nerds like me
When I Do Uh My Best, System 1 is operating. More information about System 1 can be found in this blog post.

WYSIATE stands for What You See Is All There Is. If I am too busy, I forget to look for other relevant information as mentioned in Thinking Fast and Slow.

The Lindy effect is about using knowledge especially from books. Thinking Fast and Slow is quoted for years by some testers. If a book is relevant for 5 years, it will probably remain relevant for another 5 years.

Training Train of Thoughts

This would be a quick test. The cells in a table had been minimised, so an empty cell had been displayed like a rectangle with the height of a few pixels. Now it had been fixed.

I used some scripts to install the latest version. I put some test data into it. Then I modified the view. The empty cells were as big as the filled ones. Case almost closed.

I quickly browsed through the description of the ticket. The impact of the change was minimal or nothing. The table was used to show information. There was no way to modify the contents of the cells, either filled or empty.

Then I noticed a comment of mine. It could also occur in another application. The same functionality was used by a different application, so the developers would have reused the code. This is an obvious assumption and it was more plausible by the use of TDD.

Some explanatory stuff ahead.
Test Driven Development or TDD is a continuous cycle of test, code and refactor. During one of our Cleancode sessions uncle Bob told about this approach:

  • Make a test, that fails.
  • Make code, that let this test succeed (and of course all other previous unit tests)
  • Improve or refactor the code.

An example of refactoring is to reduce the occurrences of the same piece of code. If it is in one place, the dev has to fix it in one place.

Refactoring can also be used in making automated tests or manual test cases. Knowledge can also be refactored. The knowledge management system is my best friend. Specific information is stored in one place accessible for everyone in my firm.

Where was I writing about?
O yeah, testing the absence of minimised cells in another application.
Right. So I installed the other application and put some test data into it. I tried to find some empty cells, but that was not possible.

Thought while blogging
I could modify the input file, but that was an invitation to errors.
Sorry no access.

Let me continue with my thoughts.
I looked at the table and thought about the installed database client. Good. I opened the application and connected with the right database and the right table. Then I emptied one cell. And the cell was shown minimised on screen. Hmmm. That was not right.

Because I sat in the same room as the devs, I knew who had worked on this ticket. I told him about my finding. This could easily be fixed.

Then I tried to find out, why it was only fixed in one application:
“I put it in the comment.”
He did not read the comment.
“Okay, what can I do to fix this? Put in the description?”
The dev said, he would definitely read it. Even it was an assumption from my side. He had no problems with it. OK fine with me.

After a couple of minutes the dev made eye contact with me. He told me it was solved. I installed the other application. Just fivesome clicks.

I started the application. Nothing happened. Another reinstall followed by unsuccessful start. I opened two logs to find some clue, but there was nothing special to be found. So I asked another dev. He listened to my story and had a quick look in the logs. Back at his workplace he discovered a process that was still operational despite the reinstall. So a script had to be fixed.

Then it was time to go home. You know family waiting for daddy to join dinner.

The next day I could finish my test. There is no such thing like a quick test.
This might lead to a heuristic.

That Feeling a Lone

After my talk about a performance test I spotted two other speakers. I just joined their conversation: “How did your talks go?” A moment later I heard Rik Marselis asking behind me: “Han Toan, how did your talk go?”

The other speakers turned their attention to me and I talked about testing. Then I remembered Rik. I turned my head, but he was gone. That evening I did not spot him anymore.

Later that week I mailed him a 20 line mail about my talk.
Did I do this, because he is a known tester in the Netherlands?
No.
Did I do this, because he was the president of TestNet, the Dutch Special Interest Group in Software Testing?
No.
I wrote him, because he was really interested in my experiences. I just sent him a Reverse Polished Notice.

@ Conf Alone
A few weekends ago a speaker reflected on a test conference. It was good, but it was difficult to make real contact. There were only 2 tweets which lead to a massive discussion. The second tweet touched the members of the test community. People were suggesting solutions and sent words of support. In turn this lead to strange reactions like “It was a great conf and I felt inclusive.”

It all boiled down to the question: what would happen, if I join a conversation? To be more precisely, if I join a conversation midstream.

Suppose you are the chairman of a meeting. All participants are people you can talk with freely. At one moment two people want to say something. You pick Cecilia and John has to wait. After Cecilia had her say, what would you do?

When I come home, my kids really want to share some stories with me. I hear the first sentences of different stories from different kids. So I have to pick. What would I do after one story has been told?

I am not really super human. Luckily, my wife is taking care that I am taking care of …

Getting Personal

Suppose I have a good friend. She is already dating a man for a month. She is still hesitating And sure I want to help her.

Suppose that evening I shook hands with a good looking man. His flow of words muted me. He had a Porsche, he had a good job and he would fly to Spain just for fun. And ..
It was like a salesman selling himself.

Suppose my friend expected an honest advice after an one directional overwhelming monologue.
What was I supposed to say?

“And here’s to you, Mrs. Recruiter
Testers love you more than you will know
Wo wo wo
We need you, please, Mrs. Recruiter
Office holds a place for those who say
Hey hey hey, hey hey hey”
[On the melody of Mrs. Robinson]

Let me get this straight: I am not looking for a job.
Another straight thing: I am badly surprised the way recruiters approach me.

It goes like this:
Hi Han,

We noticed your profile on AllConnectedNow.com. And we are looking for someone with your background.

Our customer is a well-known international company. It is number 1 in medical software in EMEA. A new product will be developed in the coming years. You can be in this team.

The candidate must have
At least 5 years of experience in software testing
4 character Test certificates
Seniority to help junior testers
At least 5 years of experience in automated testing
A background in medical software is preferred.

If you are interested about this job, please call us at 123weneedatester or send us a mail.

Regards,


Mrs. Recruiter

Some people would enjoy this mail. I don’t. Apart from the fact that my profile had not been checked properly, it is not really personalised.
Let’s say Cecilia has the same background I have in juggling. She can juggle the devilstick, pass 6 clubs, and has an act of 3 minutes. Excuse me. It was about software testing, but I only read the word background.

Let me start again. Cecilia has the same experience in software testing I have. I could start the mail with “Hi Cecilia”. And it still make sense. Another straight thing I want to share: I do not know a Cecilia with this profile. I just made it up to make my point. So if you did not find Cecilia, that’s why. By the way AllConnectedNow.com does not exist for the same reason.
I like recruiters who can spot senior testers, but I have some suggestions to connect. That’s fine with me and hopefully you.

Last months I got several friendly requests to exchange thoughts about a new job. The mails looked like the one I described. Why me? So I politely asked why they would have me in their team. The answers were .. Let me put it this way: I did not receive an answer on this question.

I felt like a number. It could be 8 or 754. So if a junior peer would ask me about this company. I am not jumping up and down for her or him. It’s just another company.

Of course some recruiters might like numbers: “I sent 100 invitations to interesting candidates this morning.”
But a company is not happy, if they get 40 junior people who are willing to do the job. But it was actually looking for senior or expert or whatever you call her or him.

In marketing Unique Selling Points are used. E.g. a company is number 1 in medical software in EMEA. Let me turn this around. As a recruiter I would look for someone with Unique Buying Points. “I noticed you have experience with medical information systems on a Windows platform.” Or even better “I noticed you tested a Dutch medical information system on a Windows platform a few years ago.” My guess is there are about several hundreds. And it is easy to reduce the scope using “information system for house doctors”. This might lead to a number close to 60 on the Whole Wide World. I would feel appreciated as a tester.

Today the world is moving fast. I ignore commercials or invitations, if they do not resonate with me. But I do remember companies which felt right or wrong to me.

“We’d like to help you learn to help yourself
Look around you all you see are sympathetic eyes”
Mrs. Robinson sung by Simon & Garfunkel

Backtracking for testers

“I cannot reproduce it.”, I admitted to my scrum master. He replied with:
“You can do exploratory testing, but you have to note down the steps, which led to this situation.”

How did I get in this mess?
I sanitised this story BTW.

On my screen were some filters and buttons. It was not possible to use the action button any more. That was NOK. I made a partial screen shot and put it into my test charter. I would later come back to reproduce it.

Somewhat later I looked at the screen shot. I thought it would be easy to reproduce the situation. After three attempts I gave up. That was NOK.

My scrum master had a point though. I had lame excuses like no recording tools and extra bureaucratic steps. Back to The Bug. If I could find it.

A little bit of theory
Backtracking is a term I picked up during my study. It took me years to understand the principles.

It is basically solving a labyrinth: continuously pick a direction and walk, until a dead end is encountered. Then go back to the place where the last wrong decision was taken and take a new direction.
Rinse and repeat.

This tactic can be applied to find the toilet or to solve a puzzle.

Sorry for this theory interruption. I will now continue with my blog post.

A lot of practice
The first thing was to examine the screen shot again. I realised I was on the wrong screen. So I switched screens.

Then I rebuilt the situation. I added the filters with the same values. I pressed the action button. That went right. I kept my mouse on the button. It could be used again.

I used the other buttons on the screen. After a few presses I returned to the action button, which was still completely functional.

I did a reset and started to rebuild the situation. If I pressed the other buttons before the action button, then it might become insensitive. After adding the last filter I pressed on one of the other buttons and clicked on the action button. It was still functional. Business as usual.

It was time for my visual memory. The adding of the filters went from left to right. It felt great. Every time the set of available filters became smaller. It was like dealing cards. The stack became smaller and the cards were put from left to right.

I looked to the most left filter. It was a date filter. I already had filed some bug reports on that one. Wait a sec. This was my starting point for bugs. I might have set it to a wrong value and quickly checked the side effects.

The word quickly triggered my mind. I was so used to this filter, that all date filter related actions were absolutely normal for me. It became natural and therefore easy to forget. Because I moved my mouse so fast, the movement was not stored in my memory. That made sense to me.

So another attempt to reproduce my bug began. I set the date filter to a single bad number and added the other filters from left to right. And I pressed the action button. It worked. Then I tried to use it again, but that was not possible. Bug reproduced.

Now I wanted to reduce the number of steps. My assumption was that the invalid value in the date filter triggered the bug. Time for a short cut.

I reset the screen and only added the bad date filter. The second push on the action button was useless as expected. I was able to backtrack my steps and reduce them afterwards. That was OK.

At the end of business day my scrum master groaned, when I showed him the bug.
“What else did you find?”