Starwest

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— mindfulcoder (@MindfulCoder)2013-10-02 18:34:38

Maybe write test cases with the devs as a way to review stories? #StarWest #agiletesting

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:34:20

#starwest keynote room. Karaoke rocking http://t.co/kR2dSiPkqJ

— Haverford Historical (@HaverfordHist)2013-10-02 18:31:33

"Security is everyone's responsibility" via Leo Navarro (@SofttekSecurity) #StarWest

— Softtek (@Softtek)2013-10-02 18:31:18

QA writing test cases should be quick… based on acceptance criteria. 15-30 minutes max. #starwest

— Kwality Rules (@KwalityRules)2013-10-02 18:31:06

RT @g33klady: Get QA involved as far upstream add possible, when designs are created #StarWest #agiletesting

— Michael Larsen (@mkltesthead)2013-10-02 18:30:19

Visit the @TechWell crew at booths 39 & 40 at the #starwest Expo! Drop off your passport with these knuckleheads. http://t.co/EF6Ni2G6fv

— Beth Romanik (@bethromanik)2013-10-02 18:30:06

When stories are estimated it must include testing. And buffers fit bug fixing and retesting #agiletesting #StarWest

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:29:18

Ready to talk testing in the afternoon session at #starwest! https://t.co/8thJo1c1Qw

— Parasoft (@Parasoft)2013-10-02 18:28:42

User story augmentation - acceptance criteria and pictures or wireframes. Before the iteration begins #StarWest #agiletesting

— Hilary aka H-Bomb (@g33klady)2013-10-02 18:28:04