Peter Walen, Consultant
People using a computer system rarely use the features in a linear manner. They may use several related functions to do what they need to do: their “story” in the system. Other people will be using different functions at the same time. They will be engaged in their own stories. Why do so many testers and test groups ignore this simple idea? We may work using “stories” but do those stories reflect the real stories of the real users? If the users, our customers, are the ones who will accept or reject the software on its quality, can project teams and test groups adequately predict system behavior if our testing has little to do with the system user’s behavior? Join Pete in a discussion of these ideas around broader function and integration testing with a focus on understanding true business needs and operations of the system.