Whats the difference between usecase,testcase,testplan,and scenario and their templates.
How tp raise defect for for I am feeling lucky button on google page if button not appear on the page?
If at all 3 testers of a teem found same defect how to remove duplicate bugs
First of all we should not raise the defects again, which already raised by other tester. Before raising any defect we should check other defects in that particular module, release is any other tester...
Before submitting the bug in defect tracking tool, check the whether same defect is submitted other person in defect tracking tool ,this is one way of remove duplicate bugs or Before submitting t...
How to convince the interviewer for "how many bugs in ur project?"
How many bugs in ur project? What will the correct answer of this question, how we convince the interviewer regarding numbers of bugs
When we are working on new functionality of the application, obviously we will get more defects. We can't say particularly these many numbers, that depends on developers and complexity of the project,...
It is very common question that Interviewer can ask..before answer to this question we should clarify what type of defects that interviewer asking? defects can be product defects and process defects t...
Explain what a duplicate bug is ?
Duplicate bug -> is that bug which has already been reported and functionality is same as the reported one.
but sometimes developer also treat the bug occurred in different scenarios as duplicate bug, but it is different because there steps reproduction is different.
Hi Duplicate bug can be termed as following issues: *It can be like same defect we found in different scenario or attempt and reporting them in the bug tracking tool with different bug id.It might c...
What is difference between bug and defect ?
Bug: Bug is a fault in a program or application which is found when the actual result diverts from the expected result.
Defect: A flaw in a component or system which causes the component or system to fail to perform its required function. e.g. an incorrect statement or data definition.
Logically both are same.
Suppose a bug was found by the customer, as a testing what is your comments on this issue?
Review the bug to see the root cause. Then, plan and do preventive action.
Review and analyze that bug. If testers are missing, we should consider what is the gap and see how to prevent it.
Remote execution of selenium scripts
I want to execute my test case scripts kept in quality center test plan on my local machine to be executed on a different machine which only have the qc ota client using runmanager on c#. How can I transfer my test data and the other information on that remote machine through qc for the execution process...
How is traceability of bug follow?
It is adoc ensure that each and every low level req holds a minimum of at least one single test case
The flow of Traceability Matrix
s.no->Module name->high level req->low level req->req id->date of creation->revised by->test cases->author name->attachments->test scripts->defects
We can trace the bugs using above said ways, but most of the cases we followed the test case document ie just leave all the cases which are passed, logged the defects which are failed.
What more status can you give to a test case other than pass, fail, not run & blocked?
The defect status are: '->WILL N'T TO BE FIX ' '->DEFFERED '->DUPLICATE '->RFE NEW '->ASSIGNED--->FIXED->CLOSE/REOPEN '->REJECT '->NEED MORE INFO ...
Status:
1. new bug
2. open bug
3. review bug.
4. not bug (.close bug)
5. Duplicate bug (.close bug)
6. Not important(.deferred)
7. is it bug. (.assigned to developer)
8.retest
9. Close.
What will you do when developer rejects your defect?
1.if the T.E understand the req wrongly and have this issue is communicated with dev.team ex:the req is 1+1=2 but the t.e understand 1+1=11. 2. if the dev understand the req(defect) wrongly and hav...
When a developer rejects a defect then we (testers) have to check on which reason he rejected the defect.The developer may reject the bug if it is "Non Repro" or "Known issue"...
Describe error handling in the frd
@ sudhakar2068 I see that you had copy/pasted the content from else where. If it is your own paper, a link to that paper would be appreciated. Perhaps, we all can read it BUT, but if the paper isn'...
FRD : functional requirements document Error handling means application should throw error messages when user forget to enter data in some fields; or user enters wrong data. Example: user enters wron...
Welcome to Agile testing!
/sorry you are throwing different things into the mix - test cases, bugs. Can you be more elaborate and clear so that other people who are interested in knowing the question and answers can understand things clearly.
If the customer changing the reqs ... : If the change came in between the testing time of previous requirement ( change) then i can stop testing and intimated to my TL... if the change came afte...
How to import foriegn keys and user keys in EIm,and how to write ifb file.
WRONG forum!
Please post in correct forum to get quick answers
How do you measure the injected defects?
One way to reduce the escaped defects (defects discovered by end users) is to reduce the injected defects (defects introduced by the project team). How do you measure the injected defects?
By acceptance testing n beta testing
One example where you could not find the bug in black box testing but you can find in white box testing?
Memory leak, as it will effect functionality but will effect performance
Memory leak, memory leak will not affect the functionality but it will affect the performance, if you are not using any specific tool to test this then it will not be caught by a black box tester. there could be some other examples also
1. User interface defects -------------------------------- low 2. Boundary related defects ------------------------------- medium3. Error handling defects --------------------------------- medium4. Calculation defects ------------------------------------ high5. Improper service levels (control flow defects)...
Raaj sorry to say but in ur bug life cycle dev doesnt reassigned to tester its the test manager
Severity varies between scanrio to scenario. Input Domain Bugs Error Message Bugs Calculation Bugs Critical Bugs Hardware Bugs Load Scenario Bugs Source Bugs Version Control Bugs ID Bugs
Different types of bugs :
User Interface Bugs
What is defect life cycle in manual testing?
It is the process of fixing the bugs which tester or any of the team member found in the development phase,
Defect Cycle is :--
1)new
2)open
3)Fix/Deferred/Not a Fault/
4)Restest if it is a fix.
5)Reopen or close accordingly.
Yes definitely if the bug is of high severity it needs to be fixed even if has low priority if the end user will find it will cost huge for company and can also effect on company status
To answer you question in simple terms: YES it is possible to have a bug with high severity and low priority and vice-verse. Priority is from the view-point business, and severity is from the techn...
Closure action taken by tester
As a tester you found lot of defects/bugs in the entire test cycle. As the release date is near (within a week), you found many of the defect (24) is not yet closed. What are the closure action you will take?
Action items: 1. Determine how many are Priority 1 (P1), 2 (P2) and 3 (P3) bugs. 2. Send an email to all the project stake holders - BA, PM, Dev lead, QA manager, QA lead) with the # P1, P2, P3 out...
Some pieces of the puzzle are missing but let me attempt to answer What is the length of the test cycle? At which stage of the Test Cycle are these bugs reported? What are the Priorities / Sever...
Use Case :use case is a document which explains the purpose and use of a particular functionality in the way the end user use the functionality in business. Test Case :Test cases are the set of cond...
Usecase: Usecase is prepared by BA in the Functional Requirement Specification (FRS) which are nothing but a steps which are given by the customer.TestCase: It is prepared by the Test Engineer based o...