Monday, May 10, 2010

Rorschach, the power of visualization and software testing?

Introduction
I blogged about my experience in Weekendtesting were I used Astra Site Manager creating a map WTANZ02: Same Language, different sites and places. In that post Shrini Kulkarni challenged me to expand on how to use this as test strategy.

When you look at the images posted there, you might notice that the images look a bit like spots/stains.

Rorschach test
When thinking about spots/stains and deriving information from it reminds me immediately on the Rorschach test.


From Wikipedia: Rorschach test: "also known as the Rorschach inkblot test or simply the Inkblot test) is a psychological test in which subjects' perceptions of inkblots are recorded and then analyzed using psychological interpretation, complex scientifically derived algorithms, or both."


Below you see an example of a Rorschach image. Are you able to read this picture? Are you able to assign functionality to areas? Do you see bugs?

Image saved from wikipedia http://en.wikipedia.org/wiki/File:Rorschach_blot_01.jpg

Primarily based on the perception of these spots the user is asked what and how he experience this and why. What does the spot tells you.

Testing spots

Below you see the 2 images I obtained from "testing" the 2 websites as stated in the challenge from WTANZ02: Same Language, different sites and places.


Just tell me: what do you see?

Image 1


Image 2

It depends how you look at the images, you might identify some shapes. Perhaps you only see dots or animals. Perhaps you see bugs.


The strategy
Defining a strategy is a challenge itself. Writing about it and sharing your idea is even more a challenge. Writing about it and trying to come with a Heuristic is more challenging for me as this is quite new to me. So bare with me, support me and make me teach you as I can learn from you.


First steps
I suggest first to define the approach based on patters. Ask what the image itself can tell you and what information do you need to define the approach.


Imaging: Create a map of the website/ functionality to define a certain landscape
Defocus: Don’t approach the image as a system, approach it as a painting, approach it different, what else do you see? Use your imagination.
Interpret: Are you able to tell a story about what you see (colours, lines, drawings, etc.) and argument it?
Density: is there a structure available representing the first impression you had?


Next steps
After you got a main overview about what the system could look like you might play with the following components.


Complexity: Is there some kind of structure? Are there lots of nodes and are you distracted by it?
Number of objects: Are there too much objects visible you are not able to zoom in without missing details?
Environments: Can the map also be used to identify other systems/ secure areas?
Risk Areas: Are you able to point areas of risks in the map based on "important" functionality?
Process: Is there a order available in the structure which also might support any process?


Other steps
Looking to the previous actions, I hope to provide some additional ideas how images from a website structure can support defining an test approach. I believe looking on a different way to images or structures you might come up with other concepts and thoughts which supports your test approach. The next step could be adapting the newly gained view into your test process. Based on this information you can define alternative test cases or perhaps product risks analysis.

It might help to get back some creativity back in testing.

2 comments:

  1. >>>Below you see an example of a Rorschach image. Are you able to read this picture? Are you able to assign functionality to areas? Do you see bugs?

    First thing that came to mind (to ask about the picture to a subject) is "describe the picture".
    with this question you can gain lots of information about how subject is thinking about the picture. You can use the picture as an interview question and ask the candidate to write down the 1 page description.

    In such situations, I don't necessarily think in terms of software, functionality, bugs - rather I think of it as an "interesting problem" of systems thinking.

    Based on how broadly or diversely a person can think, we can gain good understanding of person's visualization capabilities. Just ask people to describe a picture like that ... see you will be overwhelmed with responses.

    Seeing patterns, many of them in a maize of information (multi-sensory -> Visual,audio...)- is my opinion a great systems thinking skill.

    Read "Outliers" from Malcom Gladwel - you will appreciate "seeing patterns" in data.

    >>>Defining a strategy is a challenge itself. Writing about it and sharing your idea is even more a challenge. Writing about it and trying to come with a Heuristic is more challenging for me as this is quite new to me.

    You seem to be on the verge of developing an interesting modeling technique. It might be helpful to think of this whole thing of visualization (that is the core theme of your idea) as a modeling technique to represent "test object".

    Think of generalizing the idea of visualization as it applies to gaining and representing information about "test object".

    I believe, at this stage you need to worry about test strategy, heuristics etc... Focus on getting your articulation broad and deep about "visualization and modeling". I think that should be your line of thinking....

    Mind maps, Finite state machine diagrams, network topology diagrams - work as visual models to communicate information.

    Look forward for more on this...

    Good work ..Keep it up

    Shrini

    ReplyDelete
  2. Hello Shrini, thanks for your feedback. You provide me good directions to work with. You correct about asking first what you see; instead providing already some direction.

    As far as I see, this way of modelling can be an addition to “formal” ways of interpreting data.
    Indeed I have to work on heuristics and how to formulate and use them. For me this weblog is also a tool for practice and learning. Your feedback is very welcome. In my opinion, trying to translate a strategy to heuristics is harder if you don’t yet have all the skills :)

    Seems I’m reaching my goal, learning as result of my blog.
    Thanks again.
    Jeroen

    ReplyDelete