January Testing

Somehow I ended up with this test term or test type. Actually is a subset of boundary value analysis. But I got your attention.

That’s my right

It was the second day of the year 2018. I was about to place a new post on my web site. I just knew something was wrong.

I went to the web site lay out. It took me a few clicks to open the footer. Then I changed the text to
“2014 – 2018. Mindful Tester. All rights reserved.”

Now I could add my post.

It is my right
for which I fight

That’s my audit input

The same week.
For the audit I ran a query in the defect registration system. The number of items on the list was startling low: 0. My query was wrong. That bugged me. Last year it gave the right results. Actually a few weeks earlier.

I had a look to the query and noticed:
I don’t know all the commands, but I could make a good guess.
This year started at January 1st 2018. I was one year off.
The report was about 2017 and not about 2018.

A few hours later I had to go to my boss. He still used the same old query. It was easily explained.

It is not the query
I marry

A test idea approach

Let me generate some test ideas:

  • Is there a checklist for things to be updated in the new year?
  • If yes, so when is it updated?
  • Are queries based on fixed dates instead of relative dates?
  • Are there changes in laws which I have to pay attention to?

Still wondering about the pic with door?

Janua is the Latin word for door.

What about May 2018 testing? Excuse me GDPR testing.
Do you know what the effects of the General Data Protection Regulation are? An European customer has the right to be forgotten. But what about payments?


Hide or Seek Outside the Comfort Zone

You can only listen
Aaltje Vincent about Twitter

The day after Christmas I saw a question from Kim about test types on Twitter. She could not find the desired information. I remembered a long serie of Jean-Paul about test types.

I did a quick search on the internet and found some useful definitions. On my reply a most grateful reply returned. Twitter can be quite helpful. In deed.

The truth is out there.
Special Agent Fox William Mulder

In order to prepare my tests I use Gherkin to describe my test ideas. Okay. I slow down a bit.
In the defect registration system I can add comments. I use Gherkin, because it is a high level language. It saves me the pain of dealing with all kinds of technical details. Which can change of course. Which is out of my control.

The devops in the team use Gherkin for their unit tests, so they can use my test ideas in case of jumping in. One devops tends to browse my scripts with test ideas. So it actually saves me time and I can do more exploratory testing. The unit tests are quite thorough.

One day I was looking for test ideas for removing items. It was simple and therefore deceiving. I did my run with SFDIPOT.
O stands for Operations, how will it be really used?

I imagined the users looking at the same item. What would happen, if two users would delete the same item?

I stood up and saw the devops who had the best overview of the system. I walked a few meters and started a chat about the simultaneous removal actions. He listened and agreed that this should be taken care of.

My scrum master joined in with a minimum of words: “Race conditions”.
Back on my desk I searched for race conditions.

I felt comfortable when I asked my question. The 2 words of my scrum master increased the safety. For me and the others

Ask yourself, “What would my cheerleader say to me right now?”
Denise Jacobs

One of the best things about the testing community is 30 days of testing. On twitter you can find a lot using the search term #30daysoftesting. The hash tag is a label which can be used to find relevant information or questions. E.g. #testing, #softwaretesting.

One of my best Twitter months was July 2016. There were small and big challenges in 30 days of testing and participants were encouraged to share their progress on the internet. Testers over the whole world participated.

I liked the atmosphere. Trying to create strange tweets which still fulfilled the challenges posed. Some of my tweets got likes and I became more comfortable with Twitter. It was possible to share my thoughts about testing. With people I never met.

I think #30daysoftesting is great. Thanks for making it happen
Bret Pettichord

“Just name two people who are quite influential in the test community about complexity.”
“Let me guess.”
“Hey I was first. To let you guess.”
“Dave Snowden and Nassim Taleb”

“Why those two?”
Snowden made Cynefin. For me it is a model how to handle in certain situations. Nassim Taleb made INCERTO. He focuses on becoming anti fragile.”

What was I struggling with?
Is there any relationship between Cynefin and INCERTO?

So I used Google and another search engine. I could not find something on the web which addressed my question. With a bit of luck this is the first one with a first step.

The same day I answered Kim’s question I looked to the tweets from Dave Snowden. He was busy with the principles of antro-complexity. He welcomed questions. For three days I had been polishing my question.
So I tweeted my question how these principles did fit in the genealogy of INCERTO.

I got a reaction.

Without doubt, you have to leave the comfort zone of base camp and confront an entirely new and unknown wilderness.
Stephen Covey