For Testers: Nihit Kaul Talks Up Model Based Testing


It was my belief as a test lead and is still my belief.  To test a product with any amount of interesting complexity you need to find good ways to reduce a reliance on manual processes.  If you test manually you need automation.  If you are writing a test plan you need to have a machine figure out the details.  If you start writing automation you need to reduce the cost of writing automation.  One way to reduce costs and start abstracting the testing problems is through model based testing.  Nihit has a good introduction article to the practice you should read. 


Internally we have gone so far as to write automation that abstracts Visual Studio, write a model that represents a feature, and have that model make calls to the automation. This reduces the cost of writing scripted automation.  Only a few teams have started doing this and I think it has a long way to go, but I would be surprised if the use of such practices don't take off quickly. 

Comments (1)
  1. Scott Duffy says:

    It appears that model based testing forces you to define the various actions your application can take (add, edit, delete, rename, etc.) and when it can take those actions.

    But I don’t understand how lower level functions are tested in this model. I mean, in your ‘add’ function has a screen with 80 text boxes that need to be filled in, how is model based testing going to help? I still have to write code to fill each of those boxes, and the code I write is still "static script".

    It appears model based testing is a series of static scripts instead of one giant static script. Is that correct?

Comments are closed.

Skip to main content