integration testing

pukars4u · Post by **pukars4u** » Thu Feb 23, 2006 8:32 am

How to do integration testing

using Control jobs

is there any proper way of keeping the jobs to run in ctrl jobs

help will be appreciated

ArndW · Post by **ArndW** » Thu Feb 23, 2006 8:50 am

Whole company departments do nothing but integration testing and there are books written on the subject as well as over 50 million google pages that match "integration testing". So the answers you are going to get here are only going to scratch the surface of what you will need to know.

So all your jobs and perhaps even sequences have been unit tested and you wish to see if they all will work correctly when run together. It is initially a matter of defining your results and then comparing your actual run with those results. That can be tough if you are doing new coding or easy if your "unit" replaces an existing system. You will need a distinct DS installation as well as a distinct data and database area that is sufficiently large to hold your data.

Could you explain what you mean by "is there any proper way of keeping the jobs to run in ctrl jobs "?

ray.wurlod · Post by **ray.wurlod** » Thu Feb 23, 2006 2:15 pm

Are you asking whether there is any mechanism for preventing jobs from being run independently, only allowing them to run under control? The answer to that is yes. Add a few lines of job control code that detect the name of the job's controller; if there is none, then issue a stop request.