starwest

You need to become ONE team @grabnerandi #StarWest get into the sprints, get into the meetings. give inputs!

— ChrisG. (@ChrisGlaettli)2013-10-02 15:05:48

#StarWest via @INXPO

— Wendell Jones (@wjones907)2013-10-02 15:05:40

Don't restrict testing to the explicit requirements. Use your brain's implicit requirements as well. #starwest

— Kwality Rules (@KwalityRules)2013-10-02 15:05:15

RT @lloydke: Automation's job is to free up testers for exploratory testing. #starwest

— Tim Western (@Veretax)2013-10-02 15:04:32

Root cause for lack of performance: more and more release cycles, more and more devs and no focus on performace @grabnerandi #StarWest

— ChrisG. (@ChrisGlaettli)2013-10-02 15:03:22

Automation's job is to free up testers for exploratory testing. #starwest

— Kevin Lloyd (@lloydke)2013-10-02 15:03:18

RT @melissatondi: #STARWEST there's no such thing as the "best" tool. With your automation strategy "What's the most suitable tool?" is the…

— Tim Western (@Veretax)2013-10-02 15:00:49

RT @aclairefication: @grabnerandi talking about customer usage expectations and planning for production (e.g. resource pools) #StarWest

— Tim Western (@Veretax)2013-10-02 15:00:44

The fact you spent tons of money on a testing tool doesn't necessarily mean it's the right tool for a particular job. #starwest

— Kwality Rules (@KwalityRules)2013-10-02 15:00:28

Imagine that, running tests against a smaller 'data set' in development may yield different results if run against production db. #starwest

— Tim Western (@Veretax)2013-10-02 14:57:59