How Model Based Testing solves traditional testing issue of keeping test cases updated with requirement changes.

In product based companies, biggest challenge with testing is maintaining test cases. Few reasons for maintaining test cases are a) to keep test cases up to data with respect to requirement b) that test cases document being a live document, it needs to be understood and maintained by new testing resource.

Suppose if Tester A writes test cases and later if Tester B role to maintain. Tester B needs to know with what level of understanding Tester A has written those test cases, because without that Tester B cannot modify or delete the test cases. This is one of the biggest problems companies are facing. If the test cases are very few, then it would not be an issue, but when we say product, it will have near to 1000’s of test cases. When there is a change in the requirement and if tester needs to maintain, then it is very much time consuming.

Can Model Based testing solve this problem?

Yes, when Tester A understands the requirement and creates a model, complete test artifact will be generated from the model automatically. When Tester B needs to modify the test artifacts, and walks through the model, it will be very easy to understand. Later one can modify the model as per the requirement change and generate test artifact automatically.