john william

• Nov 4th, 2005

 

evalution of tool

Idetification of teting scenario

desing and development of testcase

review of test cases and approve

execution of test cases

defect tracking and bug reporting

mirajay

 Profile Answers by mirajay 

• Nov 15th, 2005

 

A small correction its not "steps" they are called stubs

In normal programming if a person writes two functions

say FUN-A and FUN -B

Lets assume

If FUN-A  calls FUN-B and

Fun-B returns some value to FUN -A then

To test the FUN-A we will consider FUN B works fine and put  one stub in place of FUN-B(just remove entire logic and just return only the value expected by the FUN-A)

 if the expected result is same as the actual result then we consider FUN-A is working fine if anything wrong then FUN-A is wrong

Just isolating the FUN-A for finding the problem in FUN-A

Same way we apply to FUN-B in this case we will supply correct Values from FUN-A(removing the logic in FUN -A) to FUN-B and check the logic of FUN-B in isolation. So empty FUN-A driving the FUN-B here to find problems in FUN_B

prasuna

• Nov 16th, 2005

 

Hi,

In the Question the thing should be stubs instead of steps.

Drivers and Stubs concept comesin Integration testing.

Drivers- The one which replaces the main module is called driver.

Stubs- The modules which can replace submodules is called stubs.

Drivers come in Bottom-Up approach, where as Stubs come in Top - down approach.

kalampally

 Profile Answers by kalampally 

• Jul 12th, 2007

 

In the question it should be stubs
well comming to question
both of them come in integration testing in small

Stubs are the called compoents n are used in top -down approch

drivers are the callin g component and are used in bottom-up approch