esconfs

@cartoontester Regulations hint that testing should be kept separate from the rest of development @esconfs #esconfs

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

@cartoontester Mindeset pitfall #4 - Requirements typically good, default testing type is RBT andcan be only type used @esconfs #esconfs

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

@cartoontester Mindset Pitfall #3 - New tools must be validated prior to use in regulated environment. @esconfs #esconfs

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

@cartoontester Mindset pitfall #2 - Not trying new processes @esconfs #esconfs

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

@cartoontester Reason? Avoinding raising issues in formal testing avoids documentation of issues and logs, saves time @esconfs #esconfs

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

@cartoontester Mindse of formal testing: Trying to pass all of the tests. @esconfs #esconfs

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

@cartoontester Tester's mindset influenced by the regulations - concentrating on documenting effort rather than effort @esconfs #esconfs

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

@cartoontester Realty of formal test process is Test Plan, Test Scripts, Test Report, Issue Logs, Screen Shots, Review @esconfs #esconfs

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

@cartoontester Experienced testers often do well at this phase, but inexperienced do not. @esconfs #esconfs

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

@cartoontester Informal process is hard to describe, not managed, seems random at times. @esconfs #esconfs

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