Showing posts with label Test Methods. Show all posts
Showing posts with label Test Methods. Show all posts

Thursday, May 6, 2010

A recipe for success? Are the requirements clear?

Images above words
How often did you not heard that images tell more then words. Of course we all believe that; as our project manager of also you wants fancy colour charts and dynamic results, deliver real time.
A while ago I planned to make dinner. It is one of the recipes I got from a fellow student, we even named the recipe "Drietdrap" (don't ask me for the explanation) At that time I cooked it for some ladies and they were sold. Although it doesn't look good. I will be honest, it looks awful when you see it the first time, it taste even better. Perhaps that is the deception, it taste better then it looks so therefore it is good.

I have cooked this meal more then often for friends and family, even my children like this meal. Every time I was asked to write down the recipe so they were able to reproduce. When starting this time I noticed that I wrote the recipe already multiple times and depending on the time it was more or less detailed. This made me think about the job I love: testing. Do you taste the similarity already?

Here my story for success. Enjoy your dinner!



Would this be enough information to make create the meal and also test the meal?

Words above images
Another approach to tell the same story with words.

Ingredients for 4 persons (looks like requirements?)
- 500 gram minced meat
- 250 gram mushrooms
- 1 or 2 unions
- 2 pieces of garlic
- spinach
- crème fraiche
- Boursin
- pepper
- salt
- pasta tri-colore

Actions:
Bake the meat, add pepper and salt on taste. Boil the water, chop the union, mushrooms and garlic. Add them to the meat. Heat up the spinach and add the pasta to the water when it is boiling. When it is all done remove the water from the pasta. Add the crème fraiche to the spinach. Add the Boursin to the pasta. And mix all together. now you have a lovely meal.

Are you familiar to the recipe? Do you know when you are done?

Mind mapping dinner
Like every meal I cook, I do it merely using my mind and my sense for taste instead of the actual recipe. To structure the cooking process you can you use some kind of a mind map. perhaps the one below helps you out?


Do you also see and feel it? Do you feel comfortable now there is a bit of structure? is this best of both worlds? An image and some words?

The story so far

Like always, the result you have experienced before never succeed the success you gained now. There are several ways to communicate and there always will be information missing. As tester you have learned never make assumptions. And you now the results only at the end, is it? Sometimes there is a combination between documentation, written words and models. The image below is not a correct way to explain. For me at this moment, it is a story I could have told while cooking.



Context

I provided you a few examples how you could explain cooking this meal. There seems not much a difference between cooking and testing. You have different roads to approach cooking. You have different ways to tell. If you like to cook for profession or a person who likes to cook for fun or a cook who does it because someone has to do it. It is the result which counts. We have to eat for living. Sometimes the looks and the taste don’t care. It is the value of it, is it an in between snack or dinner to survive?

In testing you have these kind of testers also. You have persons who live by the book, you have testers who act on vision and experience. You have those who are creative and willing to try and accepting to fail. As long as they learn from failure and there is time for failure.

in the examples above you will see that information can be brought in different ways. People who are familiar with the recipe or keen on learning perhaps need less detailed information than others. For others detailed information is mandatory. It is also not only the recipes which are counting, also other information related to expectations. Like I started I once start cooking this very successfully, which might be important information as it doesn't add value in preparing the meal, it colours the expectations.

The same is about how old and trustworthy the expectations are. How about I tell you that that nice achievement is about 20 years ago. I cooked over the years more often and was also successful as friends and family were satisfied. Perhaps there is some kind of additional context, designed by memories.

Conclusion

There is not one recipe for success, There are more ways to serve. I hope you learned that we should NOT ask for detailed documentation, we should ask for information needed to add value. In this case the value was when dinner was served and eaten. Less important was the order things happened.

Thursday, March 18, 2010

Are you a Sequential or a Spatial tester?

Introduction in a new way of thinking
A few months ago I got introduced to the concept of Spatial thinking. I never was aware about this kind of difference in thinking. Sometime you hear that you have people thinking mainly with their left hemisphere, other with their right hemisphere (Yes, this is an open door so let me state this before reading it comments: and sometimes you meet people who don’t think or start to avoid thinking)

Sometimes you hear people claiming that testers are thinking differently. They need a different mind set. I believe it is not a problem to think different; as long as you are open and aware that the human brain can work different for each person. This shaping their vision and awareness about testing.

Differences in thinking
The difference in thinking is explained on Gifted Development Center: "The left hemisphere is sequential, analytical, and time-oriented. The right hemisphere perceives the whole, synthesizes, and apprehends movement in space. We only have two hemispheres, and we are doing an excellent job teaching one of them."

If this is true then it is probably that our teachers, instructors and coaches also taught us also just to approach out testing knowledge based on sequential, analytical and time-oriented way.

From: Visual-Spatial Thinking

Spatial and sequential thinking are two different mental organisations that affect the way people view the world. Sequential thinking is step by step linear thinking over time, while spatial thinking is an holistic system where all knowledge is interconnected in space.

Strengths and weaknesses of spatial thinking
To understand possibilities of spatial thinking and testing you might need to see what the strengths and weaknesses are of spatial thinking. Below you will find an short listing of possible strengths and weaknesses. Keep in mind that no person is for 100% a visual or spatial thinker.

From Strengths & Weaknesses of Gifted Visual-Spatial Learners Source: Dr Linda Kreger Silverman Ph.D. Director of the Gifted Development Center Denver USA



Differences in Sequential and Spatial thinking
A comparison between the two versions is explained in: Auditory-Sequential vs Visual-Spatial thinking: http://www.gifteddevelopment.com/Visual_Spatial_Learner/vsl.htm Also see image below. When looking at it you might be forced to speak out your preferred choice. You even might suggest that Auditory-Sequential is more appropriate for testers because they are stronger in:
- Has auditory strengths
- Is an analytical thinker
- Has good auditory short-term memory
These are just a few of them. You might check them yourself


From the site Research on the Visual-Spatial Learner a research by Dr. Silverman is published providing the following facts: (I'm not in the position to check these figures and take them as proven results)

We have high confidence (over 80%) that: - At least one-third are strongly visual-spatial - One-fifth are strongly auditory-sequential - The remainder are a balance of both learning styles
Of that remainder (who are not strongly visual-spatial nor strongly auditory-sequential), - Another 30% show a slight preference for visual-spatial learning style - Another 15% show a slight preference for auditory-sequential learning style

This provides the conclusion: "This means that more than 60% of the students in a regular classroom learn best with visual-spatial presentations and the rest learn best with auditory-sequential methods. "



Sequential or Spatial Testers


When looking at the differences, strengths and weaknesses I have the feeling that the way people think has an impact on their approach and skills in testing. A person is not fully left or right thinker. Instead of seeking the disadvantages of this way of thinking we might accept it and see how it can strengthen a test process. If you accept this, you might make the next step, how to use those skills. Before you can do this you have to identify the type of thinker/tester.

Imagine what the possibilities are if you are aware of the way people thinking in communication? How about test scripts/results, requirements? Which tester would be better to prepare an overview and who have strengths in detailed testing.

I see in this topic some opportunities and will take some time to see what this way of thinking can lead me.

For more information you also might check:
In How to spot a spatial by Betty Maxwell, M.A.: "provide some clues to help you recognize those picture thinkers lurking in your environment."
The power of visual thinking by Lesley K Sword, Director, Gifted and Creative Services Australia 2005

Sunday, March 7, 2010

Weekend testing EWT08: Kept sticking in testing

The start of EWT08
I managed to attend this weekend another session facilitated by Anna and Markus on behalf of the European chapter of Weekend testing The application to test was this time Wiki on a Stick. Part of the mission was using SFDPOT
For more information see:
http://www.satisfice.com/articles/sfdpo.shtml
http://www.developsense.com/articles/2005-10-ElementalModels.pdf

Also check out the site EWT08:Wiki in your pocket for a transcript of the session

leaves me just another bit of advertisement to point you towards the weblogs of the testers who attended:
Anna Baik
Ajay Balamurugadas
Michael Bolton
Tony Bruce
Anne-Marie Charrett
Markus Gärtner

The Mission
For me this session was another great one. In front you will never know what you can learn. This time I tried to be more prepared. have the bug depository running, the screen capture tool in place, the connection with my virtual machine using Debian running, information about heuristics ready, I even read a bit again about them. I tried to prepare what questions I could ask with respect to SFDPOT.

My preparation
Like the other session I attended online it started with an introduction and testing in the first our and a wrap-up in the second hour. This time preparation saved me some time. Unfortunately, and that is how life goes, the start is different then you expected. This time I expected a tool I had to install. Instead it was sort of a webpage which should be stored on a place and could be used immediately. I was a bit distracted by this behaviour and stopped working with the idea to test on 2 platforms.

It took me some time to figure out what type and kind of application it was. While "touring" around the application to see in a quick view what the edges of the application was and what would be interesting to investigate further.

Retrospective
After wards I noticed it was hard to stick to an approach with heuristics based on SFDPOT. I remembered that the next time I should start defining the questions I want information about it. For me this is another way of thinking then I am used to like an approach conform TMap or ISTQB. Most of the time you start with a well defined process. Keep in mind that that will not work in EWT as the time is limited to an hour.

I believe that based on defining questions you can explain a bit about coverage. In this case is explanation more like picturing/telling what you have covered and what not in terms of the questions in stead of how many cases you executed and what that coverage would be.

I explained to the group that it was hard to stick to the initial idea and one of the pitfalls is start testing immediately. Michael explained that it is better to build a model first about the system. I like that idea. You can build a model based on documentation. I think reading the documentation with respect to the heuristic model can help you defining you questions.

Value of documentation and model
Building an initial model based on documentation is in my opinion a good way to start. This seems to look similar to other methods: reviewing intensively, defining all objects, prepare test cases. And then start testing.
Off course everything is sort of based on the Deming-cycle: Plan-Do-Check-Act. Only a lot of approaches are made too robust and formal that you loose time in documentation. And try to strive only for perfection instead of a good mix of result within in conditions.

The goal of documentation is mainly provide information. Based on this information developers and testers are lead to define their approach for building and testing. If the information is weak then the chance for mistakes are bigger. An option is to formalize a process of reviewing and adjusting the documentation to details to narrow the perception and vision of the people who has to build and test it.

To start with reviewing is an approach which might work when time is unlimited. A mistake can be to collect all information, judge the information, derive test cases based on that information and sell an advice based on the test results.

How about first building a draft model of the system and the environment? You can document this, you also can make a draft picture of it or make it up in your mind. Based on this you define your boundaries where to look at. If information is missing, you ask the owners/stakeholders. Keep in mind the time you have. For example: during EWT08, we had the program manager also online, we had only one hour available and instead of claiming and demanding information we tried to find our own way. We could have asked a lot of questions which would extend the hour testing.
This would be another way of receiving information about the system.

Information about the system
Seems that information about the system to test is important, the time window is also a leading factor this in combination of the quality of information. It turned out that the available information for this application was harder to get. Some testers who paid thoroughly attention to that and made a remark about the documentation.

Looking back it turns out that information was available in several ways:
- online manual
- in the tool itself (written information)
- the tool itself (functionality)
- people online (the project manager)
- people online (fellow testers)
- bug repository
- information regarding heuristics like SFDPOT

The needed information was different. My approach was focussed more on the functionality and there were I found something interesting Itried to find the information within the tool. this approach distracted me as already mentioned.

A lesson learned
Lesson learned here: Create a model of the system and see what kind of borders you will find. Check this with respect to the environment. The next time I would explicitly ask me questions like "how it will work when using a USB stick." I would build a framework of initial questions using the SFDPOT and during the tour I tried to refine the questions. afterwards I would try to validate if the answers to the questions are enough to make a statement of it. This can also be a statement of gaining too less information.

I believe we testers should be careful to provide a judgement about systems. When will you know you spend enough time and gained enough information? The challenge here is that we are asked to provide an objective advice although the information mostly is translated based on subjective experience.

Monday, February 15, 2010

Test Automation by the book

Previous title was: "How TMap Next is used for automated testing" changed it into a proper title :)

Automate testing is hot. It has been hot since I work in the software testing business. It will be hot for a long time now. Often I hear arguments about automated test tools are shelf ware.



Sometimes I hear automated testing by the book is not possible. I might have formed an opinion that the Test Approach: TMap Next by Sogeti fails when it concerns automated testing.

When I think and talk about automated testing I think how to use tools and not how beautiful tools are. Sometimes you find another usage of items and methods. Recently I found someone using the Test method as written to automate his testing.

As you see, the book contains the method and it is used to automate his testing. Therefore the method is used for automated testing. In this example it was used to support the LSMW (Legacy System Migration Workbench) in SAP. An LSMW is a tool that supports the one-time or periodic transfer of data from a variety of sources without any programming. Only in this example it had to ran multiple times and therefore user interaction was needed to press the Enter button. As you see. The book/method is very useful to support in automated testing.

As you see the book is lying optimal on the "Enter-key". You might consider this as a steady firm tool. As some testers which are familiar with the "old"Tmap approach, we have been told to use it as a tool not as a goal. I think this is a good example to use a method as a tool.



To order this book as a tool you might take a look at: TMap next

Friday, January 22, 2010

Of all models a W-model

Last Wednesday I attended a meeting from the Dutch Testing Organization TestNet related to W-models. During this meeting 3 guest speakers: tried to sell their vision about a "W-model".
Of course we all are aware of the V-model. We are also aware of reviewing and how it can contribute gain faster a vision about the quality.

Egbert Bouman: explained his view towards a SmarTEST W-model which represents more the iterative approach of development and the interaction with business
Jan Jaap Cannegieter: informed us about the historical mentioned W-model referring to Paul Herzlich who already spoke about a W-model in 1993 (source: http://gerrardconsulting.com/?q=node/531). He explained why and how reviewing methods adding to the well know V-model created a "W". He is also one of the co-author of a very good book about reviews (Dutch: "Reviews in de praktijk") In his W-model the moments of review results in the "W-model"
Jos van Rooyen: Who referred to his experience from already 15 years ago referring to a similar model where he added the products to be reviewed and/or the roles to perform to a similar W-model and created a "triple V-model"

The outcome of the meeting was to choose for one of the models to be the W-model. Unfortunately history was overruled by reality? The model of Egbert was chosen.

Based on that event I cam up with some questions:

1. I always thought about the V-model as a development model. I might be a misperception from me. In the Dutch testing world we refer to the V-model too often to define and explain the testing process. We even spend time to proof that the V-model fits in other development models. Can this be done to make a development model fit into another? And why also spent this energy?

2. Another thing I wonder is why are we referring to a W-model if we speak about checking the test documentation and other information sources?

3. Do we need a model to refer to the importance of checking documentation?

Some Assumptions
Assume a V-model is a development model like DSDM, RUP, SCRUM, Spiral. If the W-model is created by adding check moments to a V-model. The this W-model cannot always be used as we don't use the V-model always. This means that addding check moments can also be done to those other models. This will results into other presentations of those models too. When doing this there is no specific need to refer to a W-model as in other models you cannot draw the "W".
Assume the V-model is not a development model. It is a representation of a model like de sequential Waterfall model. Then again, if a processes of the sequential model is lifted to create a "V" we can always put them back into position so we got 2 parallel lines. In this case, the "W-model is only usable for other development models which can be supported with the V-model. Basically this can be done. Only it would be hard. Is in this case also worth to spend energy to translate to a W-model.



I would suggest to refer to the W-model to explain how reviews/checks can be embedded in a model. Only not refering to a W-model as model for full implementation.

Some other resources:

W-model from Andreas Spillner: http://squac.iti.upv.es/JTS/JTS2004/docs/Wmodel.pdf
Similar posting of W-models: http://www.testingthefuture.net/2009/09/the-w-model
The Dangerous and Seductive V Model: Nice twist here is the reference towards Morton's butterffy-model: Morton, S. (2001). "The Butterfly Model for Test Development". Sticky Minds website. Accessed 6th October 2008

Saturday, July 25, 2009

Bounded by thinking in methods and processes

It is now almost a week ago I had a challenge with Matt Heusser. One of the interesting things I learned is that approaches differ on some points. Over the years I was thought to think in processes like TMap, ISTQB , ITIL, PRINCE2. A good habit of mine is to investigate the borders of those methods.

When I was at school I noticed I drove my teachers and also fellow students crazy when questioning methods. Not to proof they will not work or they are not true. Just to investigate the boundaries of methods with the purpose to know when I cross those boundaries I need to be creative.

During the challenge I forced myself to set aside what I learned and re-shape my knowledge based on the questions I got. This helped me to find some answers and missing others. Of course this is not bad. Only there was on obvious test I forgot. Knowing it is an obvious one I forced myself thinking and start using all kinds of methods approaches etc. I noticed this brought me further from the actual solution. at the end I mentioned it, only as a side note and not as main thing. you might say I was a bit blinded by methods.
I learned that obvious things are often missed.

In the projects I worked in methods were pre-defined. In the Netherlands a method like TMap is very common. It helps you to create a structure in the test process. In almost every project it becomes a main goal to work according this method as it is already sold to create structure. When other actions are needed it is first checked against the method, does it fit in. Sometimes the approach is changed; sometimes the actions are not done because it was not agreed upon and needed as the test plan is leading. This lead to actions are skipped based on "false" arguments.

This brings me back to a phrase a teacher told me once: "Methods are tools to model your situation, keep in mind that models are just a simplification of the reality"

Based on this statement, methods and defined processes as result from methods are fallible. You never can capture reality in a model. You will always miss items. Only afterwards you might notice the importance of missed items.

When obvious things are missed based on using methods and following processes. Then, thinking in methods and processes lead to obvious blindness. The question is how huge wil this obvious blindness be? I'm sure a lot of methodologists are claiming this is untrue. There is space in methods/processes to prevent blindness. Perhaps it is. Only is this for everyone?

If everything can be dealt with by a method what level of experience and skill does one need about that method to prevent the obvious blindness? And is it acceptable to demand those level of skills to anyone? Is this reality?

A new question is: Are we dealing with reality or methods?

What would you do?
1. Accept obvious blindness and deal with it later when it fits the methods/process
2. Reject methods/processes and define your own world
3. Define space in methods/processes to address time to investigate obvious blindness holes
4. Teach project members in methods to the highest detail and claim there cannot be any obvious things which are not overseen

Sunday, June 7, 2009

Model Based Testing was this new?

I never would claim I have the knowledge. I have some knowledge and are always eager to learn. Last year I attended some conferences and one hot topic was Model Based Testing. It promised to be new and useful.

Searching for some more information about this topic I ran into this article: Model-Based Testing in Practice by S.R. Dalal, A. Jain, N. Karunanithi, J.M. Leaton, C.M. Lott, G.C.Patton, B.M.Horowitz.

Looking at the date of this article it is already from 1999. The strong part of this article I think is the focus on the method it selves instead of using tools.

When looking to recently published information the focus lies more on usage of tools. Some examples:
At EuroStar 2008 it was also a topic.

Experiences from working with Model Based Testing (MBT) and Qtronic) by Hakan Fredriksson. Remarkable is in this presentation the notation towards Rogers Adoption /Innovation curve. He shows that organizations who using MBT are early adopters. (Although it is already old for a decade)

Testing Experience: second issue 2009: "MBT as the next step in testing" by Elise Greveraars. Also her presentation on EuroStar 2008 went about how to use tools in model based testing: "Tester Needed? No Thanks we use MBT"

An interesting video by Mark Utting (August 2007) shows also an approach for MBT using tools: http://video.google.com/videoplay?docid=5521890509476590796

Tuesday, June 2, 2009

When methods can work

There are methods for almost everything you can think of, also in the field of software testing. What often is forgotten is that a method is just a representation and simplification of reality. The danger I see is using methods without questioning that method. Without knowing and checking the boundaries of a method you make unwillingly the assumption that the situation you are in is exactly as the method represents.

I hope you agree that nothing can be identically as described in the method you are tending to use. If you think so you have not only to search for the boundaries for the method you are trying to use and implement, you also have to investigate your own situation much better.

Often I see that people are familiar with methods they have been taught. Over the years they implemented and relied on them, they created some best practices for themselves. In the beginning they asked other people if they understand it correct and used it right. At that moment they were questioning themselves, the method and the environment they were into. After a while it became just a trick they performed and implemented methods the easy way, not questioning anything. I see this as a risk using methods you know. You are no longer fitting the method to the organisation; you are trying to change the organisation to fit the method so you can be successful.

At school I bothered the teachers with asking questions about the method, claiming that those are not useful. Looking back I questioned the method to understand how it works and where the boundaries are. This made me help to implement and use it when possible and triggered me when I tending to cross those borders when implementing them.

It is easy to say that a certain method is not useful; it is harder to tell what parts can be useful and what parts can be of advantage for you.

I suggest that instead of starting with methods or best practices, first start asking questions to get a picture of an organization/ project. Based on this you might be able to create a model for your own of that organization/project. Now you have two models, one model of the organisation and that one called method. Combining this with the known boundaries of the method you might be able to successfully use the method or parts of the method and become successful yourselves.

Sunday, May 31, 2009

How many documents can you create?

Often I hear the saying a good tester is a lazy tester. This doesn't mean that testers don't want to do nothing; it is just that testers just want to do just that what is necessary. Like why execute all 1000 test cases if based on test techniques these can be minimized to a number of 52?

Over the years I noticed that to control projects a lot of documentations is created. This made me curious about which types of documents I had to deal with or might have created if I follow the methods like PRINCE2, ISTQB, TMap or others.

Here a list of documents I had to face with:
- Project assignment document
- Initial test advice report (before actual testing starts)
- Master test plan
- Risk analysis report
- Product Risk Analysis Template/ checklist
- Product Risk Analysis report
- Detail Test Plan (for each phase one: SIT, FAT, UAT, PAT)
- Test strategy checklist
- Test strategy document (finally it would become part of the MTP and DTP)
- Weekly progress report
- Daily progress update report
- Daily progress templates (to gain information from for the daily progress reports)
- Deviations report
- Phase end report
- Escalation reports
- Logical test specification document
- Physical test specification document
- Test Script
- Test process dashboard
- Intake test basis checklist
- Checklist intake test tools
- Checklist test process evaluation
- Test Process Evaluation report
- Test Process Improvement Checklist
- Test process improvement report
- Checklist test techniques
- Test schedules
- Test estimation document
- Defect registration
- Defect screen print templates
- Test Execution Quick reference cards
- e-mails
- Review template
- Review report
- .....

Of course there are some more documents I had to face with. Looking at this list I just wonder: Is there still some time left after generating these documents to actually perform tests? Of course these can be all useful documents. We should continue asking the systems and the processes questions and preserving the outcome of it. Only: are we working for those documents or are those documents work for us?

Monday, March 16, 2009

All those fine test methods and approaches

There are people who think software testing is easy. There are testers who claiming to be experts in the testing area. There are companies who believe their tool is the solution for everything. There are program managers who know that mentioning a method in a plan and using templates solve all problems. There are developers who are able to use development methods as they were intended to do.

I cannot not believe we live in a world this beautiful. I'm a tester and somehow I'm an expert. In certain areas in certain conditions I know more about software testing then others. And still I'm eager to learn. This is one of my main goals. I like software testing as an occupation and as a way of thinking.

Only I believe this world is not that beautiful as it is. And we all know it. Most of the people are claiming that their methods, approaches and tools are just the way we have to work and then all problems will be solved. There are testers who work according those methods and are forcing organizations to change otherwise they are not able to do their job. They forgot that a method or approach is just a tool to help and can and should never be used as it is written on paper.

How often did you hear or did you mention that we should do this because it is: ITIL, CMMi, TMMi, Prince2, TMap, ISTQB, Agile, RUP, or whatever method/approach/ best practice? How often did you ask yourselves if it values the method or the organization?

As methods are often models how to handle things. A model is just a representation of the actual world. Models are fallible and therefore methods too. Using those methods as written makes you fallible.

Fortunately, because of human nature we are trying to avoid being fallible and we are striving for success. Preventing fallibility we adapt. We adapt our vision about methods and adjust our approaches. By doing this we have to be aware that we change the chosen methods/approach which supports the organization.

This is what makes software testing interesting for me; finding solutions under given circumstances reflecting against organizational defined methods and models using the boundaries of those methods/approaches/tools/best practices to provide information about risks and benefits for the organization when rules are broken.

Therefore software testing is not easy and we are not experts and there is not one solution. Testing is fun and should be done by people having expertise and gaining knowledge, able to adapt and having the courage to think out of the box, within the context. Testers should use their knowledge about methods etc. to value organizations instead of preaching their knowledge of a method or tool is the best solution.

Sunday, February 22, 2009

Understanding the problem: the skilled helper

How often are we offering solutions to help people based on our experience? Somehow we are trained to identify possible problems and judging them against our best-practices. Because we are always in some kind of time pressure we tending to help claiming our approach is proven and has some successes.

For example: we are asked to structure the test process and our best practice is the TMap approach. Instead of identifying the actual problems we are defining the test process based on their phases and to see what context we have to work in we perform a so called Product Risk Analysis (PRA).

For some time I'm trying to understand the Context-Driven-Testing (CDT) approach. I think the main idea here is to understand the context first before you come with solutions.

To understand the context you first have to listen. This reminded me about a book I read some years ago: The Skilled Helper: A Systematic Approach to Effective Helping by G. Egan.

I think this approach fits well in our profession also. Aren't we also "helpers"?

Egan's approach consists of three stages which might prevent us jumping into conclusions/solutions. Every stage consists of three steps with continuous evaluation (E).

Stage 1 - The present scenario: Help clients identify, explore, and clarify their problem situations and unused opportunities.




Stage 2 - The Preferred Scenario: Help clients develop goals, objectives or agendas based on an action oriented understanding of the problem situation



Stage 3 - Formulating Strategies and Plans: Help clients develop action strategies for accomplishing goals, that is, for getting from the current to the preferred scenario


I think these stages and steps can be combined with Heuristic Test Strategy Model can help define the correct context and choosing the best strategies and plans for that certain context.

For more information about Context Driven Testing see:
The Seven Basic Principles of the Context-Driven School
Weblogs:
James Bach
Michael Bolton
Cem Kaner

For more information about Egan's approach you also might check: Introduction to ‘The Skilled Helper’ A Systematic Approach to Helping

Tuesday, November 4, 2008

SCRUM: definition "DONE" and the influence of a tester

What I hear and read about the impact of SCRUM for testing differs from success stories to fear when using SCRUM. When using SCRUM a tester might have to change his perception of testing. In these kinds of projects requirements are not that solid. Documentation is not that final. How are we able to test? How can we influence as tester a development process like this?

There are some ways we can walk, here some of my ideas:

I think the power lies in the concept that the team is responsible for the delivery of a potential shippable product. The first thing which comes up in my mind is: Make sure you are on that team. Become also on of the responsible persons. Don't be the outsider test coordinator who sit down and wait until everything is delivered.

When you are on the team you can discuss about one of the concepts of SCRUM: the definition "DONE". If it is important that documentation is available and also according certain standards you have to bring this up for discussion and see if it fits in the goals of the organization that time is spend for good documentation. The same you can do with requirements.

I'm sure that there are more opportunities to help the team, the organization and yourselves. I suggest start with these 2 basic steps first.

Friday, January 11, 2008

Opmerkingen mbt TMap next (DUTCH)

Jeroen: 4/21/2008: Changed this posting as it was mainly in Dutch and Im not sure it will help someone. If you still interested in my remarks you can always contact me.

Normally I'm trying to write this blog in English. Only this would exception on the rule and sometimes rules can be broken. :)
The list mentioned below I based what I found while reading TMap Next. There is no warranty if this list is correct. It is based on the ideas I had while reading the book. I created it while reading and at that time it was Dutch. I also don't know if it represents the same pages in English. this is the main reason why not starting to translate the whole list. Perhaps it helps some one in the nearby future.

Though the list is quite long, I DO like this book. It can give good help on test projects. In other words, if I didn't like the book I didn't spend time keeping a list for myself.

Here the list in Dutch: (here the list was in Dutch)