esconfs

@TNRidgeback Wow! Loads of tweets! Thanks for sharing :) #esconfs

— Andy Glover (@cartoontester)2013-08-28 10:06:25

@cartoontester With SBTM, one critical point is that someone needs to review at the end @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:58:08

@cartoontester A bit like ATDD, where you write acceptance tests and then write code, but no automation is involved here. @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:52:41

@cartoontester Soap Opera Testing - not real life, but kind of extreme use @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:50:59

@cartoontester Looking at requirements separately, so there wasn't much integration or end-to-end, so scenario @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:50:33

@cartoontester Still do other types of testing - unit, etc. @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:49:48

@cartoontester Didn't have to write or review scripts, but did add some time to execute tests @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:48:55

@cartoontester New and Amazingly Awesome Process: RDS -> Trace Matrix ->Test -> Test Report @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:48:00

@cartoontester Old process generated a lot of waste by generating test scripts up front @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:47:10

@cartoontester Old Process: Client change requests -> Execute Tests -> Test Report @esconfs #esconfs

— Michael Corum (@TNRidgeback)2013-08-28 09:45:04