Question { MBT, 8902 }

In an Testing interview the following question asked.
who will write usecases?

Answer

use case are created by dev team and business analyst which
explain how data will flow with all below details:
1.pre-condition
2.actor
3.flow
4.success condition
5.failed condition
6.extension point

based on use case .tester starts creating test
case/scenarion by varying inputs.

Question { IBM, 67669 }

5 positive and 5 negative test cases for yahoo login window

Answer

Pre-condition:1>Login page is available...
Assumption :Approach of writing test case is based on UI
testing due to lack of functional requirement..
Positive Test Cases:
1. Enter Valid User Name and Valid Password and click "OK"
2. Check the availabilty of Edit box of user name and
password.
3. Check that OK and Cancel button are in enabled mode.
4. Check that after entering Valid user id and valid
password after clicking on tab button of keyboard cursor
should be highlighted on "Ok" button.
5. Check vertical alighnment of user id and password edit
boxes.
6. Check "Cacel button" functionality..window should be
disappeared.
Negative Test Cases:
1. Enter Valid User Name and InValid Password and click "OK"
2. Enter Invalid User Name and Valid Password and click "OK"
3. Enter Valid User Name and Valid Password and click "OK"
4. Leave user id and password field blank and hit "OK"
button.
5.Clck on the grey area of window and check behavior.

Question { NIIT, 10949 }

If the bug is found by customer and he will put that bug in
DTS , that bug is visible

1 - Dev Team
2 - Test Team
3 - B. A. Team
4 - 1 & 2

Answer

it depends upon what kind of commuinaction channel has been
agreed in test plan process.some where customer directlt
log the bug in toll and email notification trigger the bug
to allocated email id's of concerned user group.they may be
dev team,test team and or BA.


So in my point of view more or less correct answer should
be 4. in my one of company customer update the bug to test
team via email and test team log the defect in DTS and then
dev team aware about that bug.so it totaly depends what
kind of custmization and tunning has agreed in company for
suitability and profit for the project/product.

best regards,
Rakesh
Testing faculity in one of top testing institute in NCR.

Question { V2 Solutions, 7288 }

After fixing the bug, the same bug is raising again and
again in new builds what we have to do? That bug is high
level bug.

Answer

in my point of view in this scenario...pls highlight this
case to dev team (Project lead/DEv PM)to do the root cause
of repeatation of same bug since it is wasting time of
developr and QA team as well.there may multiple reasons
like...developer has not fixed and not done unit
testing..or fixed file patch not check-in check-out
correctly in build.or environment issue.so once root casue
identified then take necessary action and do through
validation before giving to QA team.