Hervey

• Oct 26th, 2006

 

Testing is testing, it's just different way of testing and it all depends on the company's philosophy as to what they consider back-end testing. Normally, during initial testing, UAT testing, Unit testing: there are certain aspects that are being tested to see if the "fix" was applied; data is pulled from production or a test environment or manually created and loaded into a file or a test DB and then the program run against this "data" and this is compared against expected results.

Anyway, this is my understanding of back-end testing.

Shasha

• Nov 8th, 2006

 

Back-end testing is like Black Box testing. Means no need to walking through the program step by step.

For Back-end testing, a Test Job needs to be prepare to execute a program, which we would like to test. Just we have to submit the Job and check whether the expected result is coming or not.

Here in this Test Job, sometime we will take complete production data or a part of production data which has been pulled from it.

Also we need to point to Test Load libraries where our changes reside.

Hope it will be helpful.

kckinney

 Profile Answers by kckinney Questions by kckinney

• May 21st, 2007

 

Without knowing your product load, it's impossible to answer your question. For example, you could have an HTML enabled CICS region using DB/2 as a backend. Or you could be doing IPv6 translation to SNA communication. The possibilities are staggering.I have over 20 years experience and am more than able to set up some testing protocols. For a mere $200/hr I could draw up an extensive plan for you.Or you could RTM and spend 20 years learning how to do it yourself.