Roles and Responsiblities of testers
I test a 20-year-old multiple application (Cobol) system with batch, online and extract components. Testing the batch portion usually requires intensive test cases with online data entry. My question is, what are my responsibilities as a tester when performing Integration/System/User Acceptance tests which require the batch portion of the system. Should I execute and baby-sit every job, only to call the programmer when it aborts, or should the programmer execute and baby-sit the jobs?
Re: Roles and Responsiblities of testers
The programmer should do what they call "unit testing" as a general rule in that the basic commands that the batch process executes should already have been checked out to make sure they work.
But then your job, as an end-user advocate, is to use that batch as the end-user would. Which, to my way of thinking, means you "baby-sit" it and report if something goes wrong with the batch process.
As a general rule, when doing "Integration/System/User Acceptance tests", as you mention, this falls to the testers.