A test that discovered more errors. The whole purpose of testing process is to discover as many bugs and errors as possible. Test that covers more functionality and discovers more errors in your software product, therefore considered more successful.


 
 

You theoretical background and home work may shine in this question. System testing is a testing of the entire system as a whole. This is what user see and feels about the product you provide. Integration testing is the testing of integration of different modules of the system. Usually, the integration


 
 

Test plan consists of test cases. Test cases you develop according to requirement and design documents of the unit, system etc. You may be asked what would you do if you are not provided with requirements documents. Then, you start creating your test cases based on functionality of the system. You should


 
 

If you never have seen automation tools before, do not try to fool around the interviewer. You produce a bad impression when “caught” on lying to the interviewer. However, if you ever used the automation tools, it would be a huge advantage for us to mention them even if those tools were proprietary automation


 
 

Obviously Testing will begins in testing phase.


 
 

Down-Top: unit -> interface -> system. Top-Down is a vice versa. You may use both, but down-top allows to discover malfunctioning at earlier phases of development and cheaper to fix than in the case of top-down.


 
 

Winrunner is just a functional Tool where as Robot, we can use it for both functional (GUI) and performance(VU).-> WR has 4 check points where as Robot has 13 verification points.




 
 

Again and again, it does not matter what bug tracking system did you use if you made your homework and invented the name of such or mentioned a standard one. You may say you’ve used proprietary bug tracking system (works especially well if you previous company was this way or another dealing with databases)


 
 

Winrunner is just a functional Tool where as Robot, we can use it for both functional (GUI) and performance(VU).-> WR has 4 check points where as Robot has 13 verification points.


 
 

defect density = Total number of defects/LOCHere the Total number of defects include the defects from Review.