Answer / pramod mallick

1) First we will try to understand system, what ever document is available or studying old system or from senior members. If nothing could be improved, then if we have time on hand, we should prepare a high level test scenarios by studying the application and execute those scenarios. and continuous improvement needs as we may need to update our test cases time to time, when we understand the application more and more.

2) When we found that there is a bug in production in our testing modules, then try to understand the bug, then try to find our the test case related to that. If test case is available, then verify how it was missed out ? is the test case is not executed, or it is overlooked. Execute the bug in Testing environment again. if this is a missed bug, then humbly report that it is a missed bug from your side. If you could not produce it in testing environment then discuss with developers to debug and reproduce it. It may be due to environment problem, it may be test case not executed, it may be test case executed but overlooked, it may not be BUG at all..:-)it is requirement but customer does not understand the flow...etc.. Just do a root cause analysis.
Post action: It it is missed out from your side, then a) update your master test case b) Update it as a learning for future.

3) Well, if similar feature is available in the application and it is not mentioned in Business document, a good tester should write a test case for this hidden requirement also.
if test case is not written, we should raise a defect through this is not mentioned in Business document and our understanding on the application is correct and discuss with senior developers / BAs to update business document accordingly.

Answer / kiranba

1) Yes, we will perform testing with the high level
requirement by doing adhoc testing
2)we will try to analyze why the defect still exists and we
try to push the patch for that bug on immediate basis ( with
extra feature in the product) so that user will be satisfies
with the product
3)first we will conform that this requirement is belong to
ours or not , if it's a one of the requirement we will rise
the defect and we will push the bug to developer if it's not
our requirement and it's affecting our feature means still
we will rise a bug in order to be in safer side . If this
requirement we not owned means we will informed the
component owner saying this bug exist in your requirement
please take appropriate action

Answer / mudaseer

1)understand the application and test end to end

2)if you have tested properly there will be no bug.but this may happen due to compatibility issue for example an application that works in one android device may crash in other android device

3)how test engineer will know that there is a bug in the code it should be bug in the application

1. What is the difference between a bug and a defect 2. What is the difference between retesting and regression testing 3. Explain bug life cycle

2 Answers   Relq,

---

Hi Friends, I have 2.5 yrs of experience. i am havung interview for QA/QC position tomorrow.what type of questions shall i expect for this experience? PLS HELP. THANKS IN ADVANCE

0 Answers  

---

What do you think is a good investment, a defect tracking system or a test management system integrated with a defect tracking tool? Please comment.

1 Answers  

---

What is your understanding regarding a test plan?

0 Answers  

---

when we want to be a good tester what should we need to be good at...

6 Answers   Semantic Space,

---

---

What is workflow testing?

0 Answers  

---

I want to know about the open source licenses and its features

0 Answers  

---

Q) Create Preffered customer: As a customer when i purchase more than $5000 in goods since my first purchase, I become a preffered customer so that i can receive the benefits associated with that status.

0 Answers   NTT Data,

---

why ur looking for change

2 Answers  

---

Need urgent answers for the interview questions? Interviewer asked 1) when you don't have enough requirements spec how did you perform testing? 2) once the project went live if you come to know that there is a bigger defect(bug) what will you do? 3) when there is a bug in the code but not mentioned in the requirement spec( while testing for some other if you come to know this bug) what will you do? I answered these questions but interviewer was not satisfied can any one please tell me the best answers for these kind of situations. I have other interview next week so please provide me the answers or can email me the answers my I'd is tester582@gmail.com. Thanks in advance

3 Answers   Maxwell,

---

What is meant by retesting? Is it similar to smoke/sanity testing?

3 Answers  

---

How do you know when your code has met specifications?

1 Answers  

---