cast2013

Having kind of a stupid amount of fun designing physical test cases for a Lego robot at @RobertSabourin 's session #CAST2013

— Clint Hoagland (@vsComputer)2013-08-26 15:11:06

Testing notifications in mobile devices #CAST2013

— Natalie Bennett (@bennett_nj)2013-08-26 15:10:51

I didn't think I was really doing anything that innovative at the time @PaulHolland_TWN about his #ExploratoryTesting board #CAST2013

— Claire Moss (@aclairefication)2013-08-26 15:09:56

Paired testing? Benefit of paired testing far outweighed getting the lower priority charters done. @PaulHolland_TWN #CAST2013

— Claire Moss (@aclairefication)2013-08-26 15:09:05

RT @aclairefication: Mention risks, costs, barriers to testing progress (resources, testability of product) @PaulHolland_TWN #CAST2013

— Michael Corum (@TNRidgeback)2013-08-26 15:08:46

@nkelln that question is for you since testing intensity isn't something i've heard before @mheusser @PaulHolland_TWN #CAST2013

— Claire Moss (@aclairefication)2013-08-26 15:08:39

@TNRidgeback Any questions you want to contribute to the conversation? #CAST2013 should have me as their Twitter community manager LOL

— Claire Moss (@aclairefication)2013-08-26 15:07:57

RT @TNRidgeback: Watching the #CAST2013 twitter feed with @aclairefication in attendance is almost like being there yourself. #KeepThemComi…

— Claire Moss (@aclairefication)2013-08-26 15:07:31

*Not* normalizing time/effort means your math won't work out. Establish a uniform metric of effort. @PaulHolland_TWN #CAST2013

— Claire Moss (@aclairefication)2013-08-26 15:07:26

Watching the #CAST2013 twitter feed with @aclairefication in attendance is almost like being there yourself. #KeepThemComing

— Michael Corum (@TNRidgeback)2013-08-26 15:07:03