Category Archives: Marketing

Q & A Bits of performance testing

“Why are you writing this Q & A?”
“Because people have questions, which are unanswered about ‘Bits of performance testing’ . ”
“Like?”
“The use of drawings and perfornance test it self.”
“So I can send in questions?””
“Sure on this page. Why not?”

“Hey, I am the one who is supposed to ask questions.”

Plan

“You used a lot of pictures. Is this not a waste of time?”
“In my blog post I drew a picture about the customer journey. This led to the conclusion that the Wifi network should be split in a private and public ones. This is not a waste of time.”
“I agree. But there were other pictures, which did not have that big impact.”
“That is right. But the drawing of picture takes minutes. Implementing the wrong performance scripts takes days.”

“You used SFDIPOT instead of another heuristic., FIBLOTS”
I am aware that this heuristic exists. I also know that a performance tester made it. And I just forgot it.
The reason I chose to pick SFDIPOT is to use this heuristic in another context. I learn by taking small detours. What if I do it in another way? My main reason was that I wanted to write about performance test in another way.
This kept my spirit high and extended my Circle of Comfort. That is a comfortable thought.”

“Your story about the performance test is sometimes difficult to follow. Why did you write a nonlinear story?”
“Testing is an activity which is unpredictable. I can find bugs on the strangest moments. This can trigger other ideas.
In this blog post I tried to describe what is going on in my head.”
“How can you sell this to your boss?”
“Just ask her or him, whether business cases are also written in a linear way?”

“I miss disk storage That is an important resource to watch.”
“You are right. I missed that one.”
“How do you know that this is a good load profile?”
“Some data have to be gathered. Think about log files and analytic stuff. The challenge is not to confuse frequency with resource usage.”
“Would you please explain that?”
“If 1000 users look to a simple web page, then almost no resources are used. If 1 user asks all articles in stock, then a lot will happen. The database is bring queried and much data is moved over the network. So look for resource usage.”

“So I only have to focus on user actions with heavy resource usage?”
“That is only possible with a very simple web site. Sometimes web sites or programs on the backend do not remove their garbage.”
“What do you mean with garbage?”

“Suppose you have a cinema web site. The purchasing department wants to know what kind of drinks and snacks are ordered in advance. Suppose all the results of the queries are stored. It might be interesting for their department and it should be stored on one of their systems. But not in a module of the web site.

Another thing is to simulate the customer. Use the customer journey. A customer does not only buys cards, snacks and drinks. She or he will also collect them. This lead to click paths, how does the user maneuver through the system: which screens will be visited and which options are used?”

“So if you have a lot of data, what do you do?”
“The challenge is to find patterns. Joe Common is more like this:”
customer journey Joe Common
“Why did you not draw the payment page?”
“It is important. I left it out because of the page size. My plan was to sketch out a rough journey. Just wait a few pics.”

“I suppose you left out snacks out for the same reason. Smart ”
“Cheers”

“Why does he go one screen back?”
“That is hard to say. You can make some assumptions or hypotheses: the price was too high. Or the wrong movie was selected. You can always ask some questions to validate the assumptions.”

customer journey no deal

“Hey there is no deal. What’s wrong?”
“Most of the yearly cinema visitor is looking around or scouting. Were there any changes in the web site? Which movies can I see? ”

child birthday party
“What is going on here?”
“A children birthday party.”
“That looks like a lot of fun.”

noted bar graph

“What are you showing me?”
“This is the number of screens and locations which were visited, and their corresponding numbers.”
“The bars in the graph are getting lower. Is this not frustating for marketing? ”
“Actually this is normal. This is a sales funnel.”

extended sales funnel

*It is like commercials: not everyone buys what they see on the television. They do not buy everything they see in the shop. You actually want people to do things which bring profit. The Call To Action or CTA for this web site is buy tickets, drinks, and snacks.”

“Okay Mr. Monologue. I’ve got a few questions.
How did you make that funnel?*
*Like this.*

bar graph to funnel

*Why do you call this an extended sales funnel? Your CTA is buying tickets, drinks and snacks.*
*But there are two moments to buy drinks and snacks: in advance and on location.*

extended sales funnels with CTAs

“If I had put the CTA in the first funnel picture, it would be cut off right under. By delaying this action I got a better view on the situation.

The second CTA is successful, if the first CTA.is good. John Common is not willing to buy extra drinks and snacks after a slow performance of the web site.”

*Are you writing that models can confuse people?*
*Yes, they do. Let me give another example.*
*Be my writer.*
*if you go twice to a cinema, you go twice through the sales funnel.

two funnels in a row
*So you should take repeat customers in account. *

For some businesses good customer contact is vital. In ‘Delivering Happiness: A Path to Profits, Passion, and Purpose’ it is called creating a moment of Wow.”

“And if things go wrong?”
“Just watch social media. Several companies have web care teams who actively look on the internet and engage with grumpy customers.”

“I would be interested in the numbers. So how would it look like?”

draft breakdown numbers

“Wait. This concept looks better than the draft one.”

concept break down numbers

“Are these estimated numbers for all visitors?”
“That is a good question. It is only for the website visitors, who also ordered drinks or snacks in advance. So I have to add a another set of numbers for the website visitors, who did not order drinks or snacks in advance and the visitors who pass the web site.”

“What is no showup?”
“That is a situation, when a customer does not get, what she or he paid for. He or she is ill. She or he found another group of friends and skipped the cinema.”

“This is strange: there are people who go to the shop without the ticket.”
“This is a common group mistake. A group of people at the cinema asking each other: “Who bought the tickets?””

“Why did you show the draft version?”
“I do not jump to solutions. I want to share my way of thinking. My thoughts and my pictures.”

“But those reversed trees with numbers is not a good starting point for scripting, I assume.”

“You are completely right. All that number crunching can take the attention away. If we have 3525 visitors coming in, then this must be translated in scripts somehow. We have to look at the chances.”
“But this is a cinema web site. It is not a casino.”

“Just have a look.”

click paths

“What does 70 % at Movie mean?”
“This means, that there is a chance of 70 % that a visitor goes from the Select Movie Window to Select Ticket Movie. You can call them of parts of click paths.”

“You are basically stating that the software has to roll a dice to determine the next step.”
“Yes. There is no single ideal path through the system. I already showed pictures of customer journeys.”

“Wait a sec.”
“Waiting.”
“The web site can easily be tested using a standard performance test, but a shop with real people is difficult. Do we need to test them? ”
“What is the system under test?”
“The web site and the shop.”
“Can you explain it to me?”
“The software supporting the web site and the shop are connected.”

“What does hold you back?”
“How can you test it?”
“I have not much experience with this particular situation. My suggestions would be: make a special interface for the shop just for performance test, mock the users in the shop, or use actual human beings. The latter option I call hybrid testing.”

“”Do you have experience with hybrid testing?”
“Yes, I have. For a web site we had to do a performance test. The visitors were simulated by the software. The web masters were real people including your interviewee. The actions of the web masters were too complicated to script, so we did testing manually. For more info there is a Dutch presentation, A performance test with a tail.”

“What is a good way to determine whether the performance is good enough?”
“A lot of people want a fixed number like a certain response time. Like the application will respond within 6 seconds. I’ve got an example.
In a performance test percentile is used: at least 90 % of the users have a response time of 6 seconds or less, if they do a specific action. This reduces discussions like:
“40 % has a response time of 5.3 seconds. That is quite good.”
“50 percentile has a response time of 6 seconds and the limit is 80 percentile.

Another thing to consider is to determine the worst realistic conditions for the system under test.”

Preparation

“Can automated tests be used with performance tests?”
“I assume you are talking about automated functional tests.”
“Yes.”
“I once got this request and it does not solve the problem. Is your manager writing a business case, a roadmap, and items for the back log for the same release at the same moment? I guess not. Every artefact has his own purpose.
But I wrote a blog post about the combination of automated tests and performance test.”

“When can the scripting start?”
“It is good to have a testable version before the final one.”
“But performance issues might still be in there. Also the interface can still change.”
“Change is always a companion of a tester. What I mean is that a tester should focus on things which will not change on long term. The technical basic components will probably not change. Test data is always needed. Data about the usage of the system is quite stable. Etc. ”

“There are always discussions about the test environment:
“We just put a part of the database in the test environment. “”
“Yes, a copy of the production environment is very expensive.
And yes, a performance test on a reduced environment can give a false impression.
I have a blog post about a huge test environment: Do you really need it?”

Execution or performance

“What would you advise during a performance test?”
“Have a hot line. If things go out of control, make sure everyone knows who to call or mail. Or your favourite communication style.”

Report

“So what should a test report contain?”
“In the report it should be described whether the performance criteria have been met. Percentile graphs are really cool. It is all about a special point in the graph:”

special point

“I would like to see some real life graphs.”
“Sure be my guest. They are on slides 14 and 15 of  the  presentation, A performance test with a tail .”

“What about the resources?”
“That is a good question. This should be covered. A nice pic would be great, but that is something for another time.”

“Thanks for answering.”
“Thanks for questioning. And thanks for reading.”

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 its’ complexity.

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.

FAQ for Tester Recruiters

An imaginary situation decades ago.
[Phone rings. I pick it up. Interested, who is calling]
I: “Hi”
Caller: “Hi. Joe mentioned you were interested in a blind date.”
I [Pleased to be called]: “Sure.”
Caller: “Are you intelligent?”
I [Ignoring the undertone]: “I am studying at the university.”
Caller: “That’ s great. Can you talk about computers?”
I [Internal sigh]: “I am studying computer science.”
Caller: “Are you attractive?”
I: “Just pretty.”
Caller: “Hum”
I [Annoyed]:”Why can pretty people have no blind dates?”
Caller: “Do you look good in a bikini?”
I [Upset]: “Excuse me. I am a man!”
Caller: “I just thought you had a low voice. Sorry for wasting your time.”
I [Angry]:”What the …”
[Caller ends conversation.]

Standard questions from tester recruiters, which are usually asked at speed date speed

Are you interested in a job?
Yes. I don’t have a job.

[LinkedIn] Can we connect?
If I do not know you, then I will not connect with you. I connect with you, if I trust you.

Would you please call me?
If you provide enough information about your company or customer, I might be willing to call you. It is also handy to provide a phone number.

Would you like to send me your CV?
All relevant information is on LinkedIn. I will send you my CV, if I am interested in the job.

Where do you like to work?
In the Randstad and the area southward to and including Breda.

Do you work and think on an academic level?
Yes. I am an engineer graduated at Eindhoven University of Technology.

How long have you tested?
In 1996 I started with my career as a professional tester. The information can be retrieved from LinkedIn.

Do you have relevant test certificates?
Yes, look at my LinkedIn profile.

Do you know the following test automation tools [tools names]?
I have no experience with test automation, but I have theoretical knowledge. At the moment I am experimenting with Selenium, Eclipse, and Java. I have more than 5 year experience with programming in C and C++.

Do you have experience with scrum?
Yes, one year.

Do you know Cucumber?
No. But I can pick it up.

Do you want to freelance?
No.

I’ve got a job for a test coordinator. Is this interesting?
It depends. I can make test plans and test reports, if necessary. But I prefer to test hands on most of the time.
Do you want to be a senior tester?
Yes. Please.

Do you know other testers, who might be interested in this job?
Yes, I know a lot of good testers. Even excellent ones. In the past I suggested some names. I did not get proper feedback, so I decided to stop mentioning names.

More preferable questions for me from tester recruiters

How can I contact you?
Just send a personalised e-mail.
What is “personalised” according to you?
If I replace my name by the name of a random fellow tester and the mail is still applicable, then it is not personalised.

Do you want to know more about my company or client?
Yes, of course. I am really interested in the way they work, the company culture, and the products / services. I am all ears.

What kind of company are you looking for?
A company, which has agile projects in house.

What is important for you?
I like a company, which is committed to go to the next test level and where I still can develop myself.

How do we stay in touch?
I prefer one contact person.

How often can I ask you something?
If there is an interesting job, you can ask any questions. Please don’t ask the same questions twice. It’s extremely annoying for me, especially if you have my recent CV.

When should I thank you?

  • After I sent you an e-mail.
  • For this blog post.

Disclaimer

I wrote this blog post on 8 December 2015. Things might have changed in the meantime.