Skip to main content

Testing and Mindfulness

How aware are you? Do you live in the here and now or is your mind always somewhere else?

This blog post is about Mindfulness. Mindfulness is a simple meditation and is defined as (According to Wikipedia):

"The intentional, accepting and non-judgemental focus of one's attention on the emotions, thoughts and sensations occurring in the present moment"

Now Mindfulness has become more popular in the west in recent years as it has shown to have benefits for people who are suffering from Depression and Anxiety. It has been around for a while and is often thought to of originated from Buddhism and some people believe it started thousands of years ago.
Now modern life is hectic and I’m sure we all have lots of things going on in our lives that keep our Brains busy and trying to focus on one thing at a time can be a challenge. I can't remember the number of times I've been doing something and my mind is somewhere else entirely. Mindfulness helps you focus on what you are doing right now and being in that moment 100%. Now imagine you are 30 years old and I tell you that you only have about 6 years of your life left. You would be shocked wouldn't you?

Well......

If your 30 and have a life expectancy of 80 you have 50 years left (I know, I'm a maths genius) However if you are only aware for 3 out of 16 hours a day you are awake, then you only have around 6 years and 3 months left of your life. And let’s be honest If you are not in the here and now you are not really living as life is probably passing you by.

So only being aware of what you are doing for 6 ish years out of 50 means you will not be totally focussed and aware of all of the great things you are experiencing.  You may say - hold on a minute I'm aware for much more than 2 hours a day. Yes you are probably right, but spend a day trying to note down all of the times you are 'in the moment' and add them up at the end of the day. Are you really aware when you think you are? Are you totally aware of the here and now when you drive home from work? Or are you thinking about the weekend, what to have for tea or how the kids got on at school today?
Luckily Mindfulness is something that you can practice and there are plenty of books and websites dedicated to how you can. An excellent book on mindfulness is Mindfulness: Finding Peace in a Frantic World by Mark Williams. It explains mindfulness and also has a CD which is an 8 week course to help you become more mindful.
This book starts you off by getting you to either sit or lay down and focus on your breath. If you find you attention moving from your breath to something else e.g. what you want for tea or what you need to do at work, just accept the thought and move your focus back to the breath.

Advantages of Mindfulness

Mindfulness has been proven to have many advantages, such as:
  • Improved Memory
  • Reaction times become faster
  • Mental and Physical stamina improves
  • People become happier
  • It changes Brain patterns

How Mindfulness can help your testing

Now how can Mindfulness help with testing? I think as a tester, where being aware of how a system behaves and what steps we have just performed is essential, then being 'Mindful' is a skill that we can't afford to be without.

Here are a few ways that Mindfulness can help your testing:

1) Make you more aware of what steps you have just undertaken.
Imagine it’s a Friday afternoon and you are testing away and dreaming about what exciting plans you have for the weekend. All of a sudden you notice an issue. You then try and remember the exact steps you performed that created this issue. You rattle your Brain and you’re not quite sure what you did. You then need to go through the entire test again and hope you replicate the steps you had previously. By being Mindful you would be in the 'here and now' and you would be focused on exactly what you were doing. Therefore you could raise an issue with the developer straight away and not have to try and replicate the steps again in the hope of getting them right.

2) Helps you step out of Automatic pilot
Have you ever had those drives to work that you don't really remember? Have you ever finished your journey and thought - Was that traffic light I went through green? If you have then you have been on auto pilot. By being on auto pilot you don't see things that you would if you were focussed on what you were doing. Imagine as part of a test you have to fill out a contact form and the functionality of this form has not changed for months. Now you may have done this 100 times before so you just jump straight into it and start entering the information you always do. Now what if something had changed in the page title? Like the colour of the traffic light on the way to work, you may have missed it because you are on auto pilot. Remember a key skill for a tester is about noticing changes in behaviour and we need to be tuned in to what we are doing in order to help us notice these changes.

3) Find more issues
The more aware you are the more likely you are going to notice things you may have normally missed. It could be something as simple as a misaligned text box or something more fundamental like how a system integrates with another system. We all miss issues but by being constantly aware you are more likely to notice issues that you may have missed previously. 

4) Take more away from conversations
Have you ever been chatting to someone and your mind just wonders to something totally different?  Then all of a sudden they say - "Got that?" And you not wanting to sound rude say "Yep" then you sit back at your desk and then rattle your brain thinking exactly what they were talking about. If you are Mindful then you are less likely to have your mind wonder and will know exactly they wanted you to get. 

5) Works well with exploratory testing
As you explore an application by learning about it through exploration and experimentation, being aware of what you are doing and how the application is behaving is essential. Being Mindful of what you uncover as you explore the application as well as how you interacted with the system could prove valuable when reporting your findings to end users and other members of your team. It also may help you question why the application does things in particular ways.

How you can practice Mindfulness

If you want to practice mindfulness I would highly recommend the book mentioned earlier in this blog post. However if you want to start straight away when don't you try the following:

1. Sit in a straight back chair with your hands on your lap and your feet flat on the floor. You need to be relaxed but your posture needs to give you a sense of being awake and aware
2. Start breathing through your nose
3. As you are breathing be aware of your chest moving up and down
4. Focus on this movement and nothing else
5. If you feel your thoughts moving away from this onto something else, gently move your attention back to the movement of your chest. 
6. Try this for 5 minutes. It doesn't matter how many times your thoughts wonder the important thing is to move your attention gently back to the movement of your chest.

Another thing I would recommend would be to pick 1 activity and really focus on it. So for example cleaning your teeth. As you clean your teeth in the morning and evening really focus on it......
  • How does the brush feel against my teeth
  • The flavour of the tooth paste
  • How the toothpaste feels in your mouth the first time it touches your teeth.
It seem like an odd thing to do but you may find that something like cleaning your teeth is an enjoyable experience once you are aware of it, rather than being just something that you do before you go to work and bed.

Mindfulness is a skill and requires practice so don't expect to do a couple of practices and all of a sudden be aware of everything. Like all things you get out what you put in.

Hope you have found this blog post interesting and useful. Please feel free to comment.



Comments

Popular posts from this blog

How to deal with pauses and timeouts in specflow

So this blogpost is in response to the weekly Specflow blog posts and challenges that have been written by Gojko Adzic. This weeks challenge was how would you rewrite or rephrase the below scenario: Given a user registers successfully When the account page reloads And the user waits 2 seconds Then the account page displays "Account approved" My initial though was something like this: Given a user registers successfully  When the account page reloads   Then the account page is displayed within a satisfactory time period     And the account page displays "Account Approved" Now the problem with this scenario is what defines a satisfactory time? You could add it as a comment or in a scenario outline but over time the time a user waits could change and if this is updated in the code behind but the scenario outline or comments are not, then what the test does and what is described do not match - this would potentially cause issues in the future. My next ide

Building a test strategy for a new team

Teams, we have all been on them. Some are good and some are bad. Some we never wanted to leave and others we probably couldn't wait to leave. Now most of the time (well in my experience anyway) you tend to get put into a team that already exists. Maybe you are a new hire or maybe you have asked to change to a different product team.  When you do this, more than likely there will already be a testing strategy in place. It may be that you adapt it and change it in any way you see fit to improve the testing. But imagine if everyone on the team was new? How would you decide your testing strategy? This post will go through some useful things you can do to help a new team develop a test strategy. Table of Contents ๐Ÿ“ˆ What is a Test Strategy? ๐Ÿค” Where should I start? ๐ŸŽฏ Understand the company and their goals ๐Ÿ’ช Play to the teams strengths ๐Ÿ‘️‍๐Ÿ—จ️ Understand what quality looks like ๐Ÿ“ Understand Scope ๐Ÿงช Understand the type of tests you need ๐Ÿ“Š Measure your success ๐Ÿค Collaborate ๐Ÿ“ Summar

Developer and Tester Walkthroughs

In this blog post I am going to talk through a new technique that I have started where me, the tester, and the developer, have a walkthrough of a change that the developer has made for a particular feature. So what are these walkthroughs?  So these walkthroughs are a time for the developer and tester to get together and for the developer to talk through and explain the code changes that they have made. By talking through the code, I mean the actual code that the developer has written and not a demo of the new behaviour. During this session, the tester is free to ask any questions, this could range from questions about the code to questions about the effect that the code changes have on existing behaviour.  These sessions are time boxed to 30 minutes and typically take place before the developer has raised a pull request to merge the changes into the master branch. Why do we do them? In short - to find issues before I get a release.... but the 2 main reasons are based upon a co