- In the first half of this year, I wrote a serie of blog posts about accessibility. Is it possible to integrate it into Agile development? I did a thought experiment with Planning Poker.
- There is a lot of talk about using multiple ways to identify yourself. For certain services is the use of multi factor authentication needed to prevent problems. It is not about technology, but about process.
- In the spring I went with my family to an in person juggling convention. My kids enjoyed the juggling. Not bad for a dad for showing instead of teaching.
- After a lot of performances, I did some acts for blind and visually impaired people. Body language and sizes are difficult to show to this audience. I really put a lot of effort to tell how things look like. How big is a duck, if I cannot pass a bird around?
- As a free time juggler, I could not resist to give some lessons about juggling to blind and visually impaired people. This took me some effort to adjust it to their capabilities. I focused on feeling.For the interested people: I did contact juggling with balls, plate handling, and tricks with rings, pois, or devilstick.
- I also gave some workshops in balloon modelling to blind and visually impaired people.For me, balloon modelling is twisting and folding balloons into a nice object. The first time I showed a white dog above a white table. This was a bad contrast for some visually impaired attendees.
- I learned braille.
- In September I got the “Gives back” badge on the Club of Ministry of Testing. I gave more than 100 likes to other posts and got more than 100 likes on my posts. At the moment of blogging, I am one of the 32 people who got this badge.
- This year I took piano lessons in piano. The focus was on improvisation.
- In 2016 I wrote a blog post about a privacy issue on LinkedIn. 6 years later I discovered that this problem was solved.
- The hardest lesson I learned was to give people the help they asked for. In the past, I gave too much information.Of course, there is a chance that these 2 facts are unrelated.
- The last months, I started to micro blog again. Once in a few days I extended a blog post with a few lines. This keeps me blogging.
- At the end of the year, I published a blog post about speaking on tech conferences. Looking at my own experiences, I noticed some specific patterns.
- A day before Christmas, the Dutch version of “Condensed Agile Testing” by Lias Crispin and Janet Gregory became available. I translated 1 chapter. I am the Chinese looking guy, who made one of the contributions or bijdragen in Dutch.
Preparation costs energy
I felt an energy drop and watched an expectant audience from a far distance. I used my automatic pilot for the intro.
While nobody moved, my distance to the audience became closer while I was talking.
I was back in the room.
First test session
For me the most elementary things of Exploratory Testing are
- Test idea
For this I created a heuristic. CTED is pronounced as See TED. If I need some inspirational talks, then I go to Ted.com.
A charter is a short instruction for a test session.
Explore < target >
with < resources >
to discover < information>
This template of Elisabeth Hendrickson is compact and informative. As mentioned in Explore it.
For the interested people test charter is not found in the index, charter is.
In my workshop the Target was a website. But it is still quite big. Resources is often a web browser.
Information was focused on privacy. General Data Protection Regulation or GDPR, an European privacy law, is still quite huge, so the next step was to select some articles of GDPR.
Ik picked 2. 1 lead to the following question:
Does the website ask consent to gather information?
A charter can be quite abstract. A test idea can be used to focus on a feature, window, or term used in the website to explore.
Consent is not frequently used, but which words are used in a web site?
Privacy, cookies, permission, private data, etcetera.
Using the charter and test ideas it is possible to explore the web site, whether consent is actually asked from the user.
During the debrief the attendees shared their information, which could be used for the following test session.
Background information first test session
For the basic structure of the test session I used the heuristic DiSSS from Tim Ferriss. This stands for Deconstruction Selection Sequence Stakes.
I assume that i was added for pronounciation reasons.
I looked to all the steps I took during Exploratory testing.
Are detailed test cases needed? Not in every case. Most of the times a good description of the precondition is good enough.
What I noticed during Deconstruction was that certain steps always came back. These steps I used for the Selection for CTED. This also led to a logical Sequence. The Stakes were twofold: people had to tell whether the workshop is worthwhile. Also the fines for privacy could be quite high.
Second test session
One test session done.
Another one to do.
At the beginning of the session I enhanced the resources with personas. For me a persona is a person with a need, who interacts with the system.
Examples for a need are: acceptance, cooperation , safety, purpose, learning, support, inclusion, etc.
E.g. a known persona is a marketeer. The more she or he knows about a website visitor, the more she or he will sell.
For this purpose I had made a set of persona cards.
I also handed out an one pager to the attendees with articles and test techniques which could be used for testing websites on GDPR compliancy.
The test techniques were selected using DiSSS.
After the Explore phase more issues were mentioned during the Debrief phase.
Background information second test session
Once again I used a heuristic of Tim Feriss, CaFE. This is an abbreviation for Compression Frequency Encryption. Once again I assume that ‘a’ was added for pronunciation.
Was it possible to compress information for testing GDPR? Yes, by making an one pager.
I tried to make to Frequency high, so attendees had to go through Charter – Test idea – Explore – Debrief cycle multiple times.
I used Encryption by using CTED.
In case you need more background information, please have a mind map.
What went wrong
The time to explore was quite short. I did this on purpose. For beginners it can be terrible to click through a site for 10 minutes on your own without finding anything.
In hindsight a group activity was better suited to explore the website.
While I tried to keep the introvert involved, it was a challenge to give them enough speaking time. I really liked the sticky notes for found bugs in the workshop of Lisa Crispin and Lena Pejgan.
My prerequisite for the workshop for a laptop was not needed. I could demo certain tools using my own laptop. Luckily there was an Open Space to demonstrate GDPR and Exploratory Testing.
What went right
The demo was a great way to change the pace of the workshop. I had good feedback during the repetitions
My impression was, that most attendees were hesitant to test their own websites or websites of their employers. My test website provided a safe environment to explore.
During the preparations I learned a lot about websites and tools.
Thank you José Diaz and your team for this wonderful journey.
During the Speakers Dinner of Agile Testing Days 2019 I told Abby Bangser about my attempts to make my workshop accessible.
“It is even possible to add alternative text to images in PowerPoint. If you click on the image, there are several tabs. One tab contains Alternative text. [ … ]
Don’t forget the exclamation mark (!). The screen reader will read it differently.”
Tobias Geyer, another speaker, was confused. I saw him thinking: “Alternative to what?”
I told him about a screen reader which could read information aloud to people. This is handy for people with a visual impairment. Alternative text is used on web sites to add more information to pictures.
If the presentation would be downloadable at the beginning of the presentation, then attendees would be able to hear the information on the slides.
Some people state that a blind review is the best one. The reviewer is not distracted by the looks of the speaker or the beauty of the pictures.
One of my reviewers was blind, so I really needed to speak well. Without the use of my slides it was difficult to tell a story. The main feedback was no clear structure.
So I added a mind map which gave a proper view of the workshop. This was really appreciated by the next reviewer.
For the exercises I had already tested the website with a screen reader. Once again it was time for the real thing.
My blind reviewer went through the website without any delay. The reading speed was so high, that it looked like a normal person was skimming the webpages. The feedback was almost instantaneous.
It was strange for me to hear, that bugs were found by clicking around. Navigation was on hearing. My test website passed the accessibility test.
The Friday before Agile Testing Days I had a talk with someone with a bad hearing. I told about my workshop. How should I speak to people who cannot hear well?
“What would be your best advice?”
“Ask whether people can hear you.
It is a professional thing you can do:
“Can you hear me?”
What also helpful is, are pictures. Next to key words on the slides.” This way a talk could be reconstructed, if words would be missed.
Somehow I lost sight on my slides.
I told about the handheld microphones seen on one of the pictures. Most of the time I put it in front of my mouth.
“It can be lowered. The quality will not decrease much, but people are able to see your mouth.” Lip reading for the win.
In the days before the workshop I focused on big fonts on my slides and my cards. I increased the contrast between the text and the background.
What could go wrong?
What went wrong?
I completely forgot to ask the audience whether they could hear me. Where was my checklist?
I had none.
The most embarrassing part of the downloadable stuff was, that there were no files on the promised location at the start of my workshop.
Big oops from my side.
After this painful discovery I repeated all the steps: I went to my github and uploaded my presentation. This time I scrolled down. A commit button?! I forgot to press it.
Github is git in the cloud. It can be used to store different versions of files. I still wrestle with it. As Janet Gregory stated in her talk it is about deliberate practice. I had only practiced once. In my case I had cut one corner too many.
Days after my workshop I checked the alternative text in the pdf file of my presentation on my laptop. I double clicked the file and the file was opened in my browser.
The text of the slide was told aloud by the screen reader. I hovered above a picture. Not a sound. I was also silent.
Last weekend I did another attempt to get some sound of a picture. I double clicked the file on my PC and Acrobat reader opened the file.
I searched a picture and placed my mouse pointer on it. A hover text was shown and read aloud. That’s what I liked to hear.
So Acrobat reader can handle alternative text of pictures, but my favourite browser not. And I had not made Acrobat reader a requisite for the workshop. A bit late, but alternative text can be used.
What went right?
I maximised pictures. Leaving out irrelevant parts from the slides.
In the right top corner of the slides I used small pictures to show the state of the test session.
During my preparation I looked at the presentation. There were no spots shining on the screen, so the contrast was good.
During the demo part I used a headset microphone. Attendees could hear me and I could talk at a normal volume. Most important is the fact, that the small microphone did not hide my mouth.