Test Beds

umm,, I think stubs refers to different components in different feilds. Nevertheless I will try explaining in telecom terms.

System: any provisioning/mediation/billing system involved

as in testing environments, there are instances when some/all of the systems are not available.
For eg: you have a provisioning system -a and respective mediation system b which talks to a switch c whichis not available. You then intend to replace/interface b with a stub of c , insense a replica of c , but not c ,C(stub) replicates the reposnes of c(switch)

b send c(switch) a job like say xyz and expects if succesfull a response 00.
now c(stub) will be programmed to send similar 00 for jobs like xyz...

i think CEans from various other fields should be able to help us uderstanding usage of stubs in their own feilds.

Durga is right.

Stubs are methods we add to non finished codes for low level methods of the architecture, they're functions that doesn't depend on other functions results to work, so we write the function definition to return exactly the result that fits the whole test.

For example:

bool Foo()
{
return true;
}

The finished function should have the required procedures to get the same result.


Drivers:

Are the same as Stubs but they have lower level functions that depend on it complete.