test objects design

Some quick loosely joined ideas:

As a Software Tester participating in building support structures of cooperative games of invention and communication of Software Development I need to know the history of a particular invention I am going to test.

Each business process, each requirement flowing from a business model of a company is an invention that supports business in growing revenue and earning profit. We need to know the history of an invention and then the invention’s usage in the context of a business model.

Let’s say I am testing a toll free number billing system. If I see that the toll free number calling was an invention then I would need to understand it to know how users are practicing this invention every day and how businesses are using this invention to create services and bill for them.

It’s not enought to just call this 800 number and test that it rings and a person picks up on the other end. There is a whole business process just for that one phone call and I would need to reason for a while to come up with a whole suite if test scenarios. To think of scenarios I would need to keep in mind the historical nature of an invention I am dealing with here even as it’s being implemented in a different context. - This further calls for separation of design from implementation. One tests design to verify that what is going to be developed is that was intended. One tests implementation to validate the assumptions of design.

Technorati Tags: agiletesting