Damage Control

I’m all for testing… I love the stuff.. but seriously, spending weeks of effort putting together a test script in the format of:Enter "Jo's super Journal 290208" as the journal entry headerEnter the journal source "Manual"Enter the journal category "Adjustment".....????It seems I've spent weeks of my life over the last 11 years writing these things. Weeks I will never get back. (There are some nice ones uploaded by other nice humans over at http://www.oracleappsblog.com/index.php/weblog/comments/oracle-11i-test-scripts/ if you’re looking for a standard test script repository by the way).Why I don’t like them, in a nutshell:too easy to concentrate effort on the test script steps instead of taking a step back and looking at the types of testing you’re doing and what sort of coverage you’ve got across the applications, particularly with regard to negative testing and scenario-based integration testing.users hate writing them and try to outsource it to the implementation partner, which is never going to work because seriously the only person who can effectively test whether you’ll still be able to do your job on Monday morning is you, not some hired gun.they contribute to the intimidating thud factor. Let’s face it – would a user would like to see a 50 page
http://jodavis.blogspot.com/2008/02/why-te040-test-scripts-for-uat-are.html