After asking the defect life cycle, if you think it is not a
valid defect, what you will do, whether you will store in
any document for future reviews,if yes, what is that
document, where you will save that document? or just reject
it and close it?
Answers were Sorted based on User's Feedback
Answer / madhavi
If the tester thinks that is not a valid defect after
loging and before sending it to developer, tester can close
the defect by adding a comment saying "User Error" so this
defect can be closed.
We dont need to store any where once the defect is opened
it will be there in your defects list.
If the defect is send to dev then it will be rejected then
tester can close it.
| Is This Answer Correct ? | 6 Yes | 2 No |
Answer / venki
Invalid defect should be tracked,thus it will help the
seniors(Lead/Manager)to identify the number of invalid
issues,it will further help the management/senior for
training programmes for the testers, pls correct me if i am
wrong.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / atul mandlik
As a tester, if though i think that it is not a defect, i will look for the cause of defect, its severity on the module or requirement under test, possible defect multiplication in later stager if allowed to go through. Will report in defect log. Discuss with project lead or team lead. Then the decision on project lead / testing manager.
If its a minor and can be resolved in next version then assign it as deferred. if decision is that its not defect, then wil close it. if defect is similar to some previously documented defects, assign it as duplicate and look for steps to reslove it. all this info cab be viewed from defect log/report which can be excel sheet or word document or defect tracking tool such as bugzilla.
| Is This Answer Correct ? | 0 Yes | 0 No |
What is Defect/Bug/Error Life Cycle?
differentiate test strategy and test plan?
how will you report defects in your company?
can any one help me? What is the Trecebility matrix ? what is that use and when it use and where it use
An engineering college wants to automate their examination activities to speed up their work and maintain high-end accuracy of information. A brief overview of the proposed system is given below: The proposed examination system is consisting of 8 semesters spread across 9 branches (assume your own branch names) and spans over a period of 4 years. Each student belongs to a branch and must register for a minimum of 6 courses but not exceed 8 courses maximum. The scoring pattern for each course is given as below: Maximum marks for each course: 100 Pass: 35% Distinction: 70% and above First class: =>60% and <70% Second class: >50% and <60% Pass Class: >=35% and <50% The proposed system computes the result and announces the results every semester. The results must be accurate and all examination records will be maintained till the students leave the college. Develop a Test Strategy to test the proposed system. Your Test Strategy must include the following: • Test Plan • Testing Methodology to be followed • Test cases • Test effort estimation • Test Correction Mechanism Note: If you need more information on the requirement specification, you are permitted to assume along the same line but clearly specify the details.
Test summary report detail
can we test the product with out documents?
if there are 10 step in test cases while executing if their is mismatch at step 5 what is status of test case ? pass or fail or pending or test not complete or else? if require tab is not available then what's the status of test case?
What is test strategy..?
how many levels of regression testing is avilable in our testing process?
Need information on Documentum4.3, any websites. What is this Documentum,how to access,features and benefits. ASAP Thx.
what are the fields in traceablity matixes.