Generally how does your team go about doing testing or automation?<\/p>\n
Most people (in my experience) jump right into writing test cases or automate written tests… anything wrong there?<\/p>\n
The source of tests is usually a bunch of written statements without any context from which testers start create test scenarios<\/p>\n
Occasionally might have a chat with the BA or product owner if they find the time.<\/p>\n
What\u2019s missing here is the context, the understanding of what problem we are trying to solve<\/p>\n
Now just if you wrote a \u2018story\u2019 doesn\u2019t mean you got all the context.<\/p>\n
It is imperative to talk to marketing, product and support to understand why we are building this product, how is our solution different from others in the market.<\/p>\n
Understanding the competitive advantage and pain points of the consumers gives the testers context and a yard stick to gauge what\u2019s important.<\/p>\n
Shadowing how the customers use the product in the field is another good way of gaining context into the solution.<\/p>\n
Any other techniques you\u2019ve used to understand the context better?<\/p>\n<\/div>