Cast2013

Reading the spec last? Interesting take on how to make sure you are creative when thinking of potential problems. #CAST2013

— Daniel A. Woodward (@woodybrood)2013-08-26 10:29:55

Investigate the product and come up with a test document before looking at the functional spec doc; keeps an open mind. #CAST2013 #QA

— Elizabeth Zagroba (@ezagroba)2013-08-26 10:28:14

RT @aclairefication: Love these prompts to broaden thinking #Testing #Heuristics @PaulHolland_TWN via RST #CAST2013 http://t.co/iwDQakW2bQ

— Elizabeth Zagroba (@ezagroba)2013-08-26 10:27:53

@PaulHolland_TWN Don't read the fund spec early, it will blind you functionally #CAST2013

— Richard Robinson (@richrichnz)2013-08-26 10:27:24

The functional spec will always be there. It's really hard to un-read. You don't want blinders func spec on. @PaulHolland_TWN #CAST2013

— Claire Moss (@aclairefication)2013-08-26 10:26:55

*Not* letting my team read the functional spec before developing test ideas really helped developing test ideas @PaulHolland_TWN #CAST2013

— Claire Moss (@aclairefication)2013-08-26 10:26:29

RT @aJimHolmes: There's something epically ironic about a testing conference's homepage throwing a 404. #CAST2013 http://t.co/SZ67n5A7U4

— Jonathon_Wright (@Jonathon_Wright)2013-08-26 10:26:29

Sources for information to flesh out the product coverage outline? Talk with other roles! designers, business, customers, support #CAST2013

— Claire Moss (@aclairefication)2013-08-26 10:25:29

RT @aclairefication: Love these prompts to broaden thinking #Testing #Heuristics @PaulHolland_TWN via RST #CAST2013 http://t.co/iwDQakW2bQ

— MyRetweet (@MyReweets)2013-08-26 10:25:06

RT @aclairefication: Love these prompts to broaden thinking #Testing #Heuristics @PaulHolland_TWN via RST #CAST2013 http://t.co/iwDQakW2bQ

— Jonathon_Wright (@Jonathon_Wright)2013-08-26 10:25:04