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.

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.

Answer / f

I think Venkini is right.

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.

what type of documents needed in every phase of sdlc for SQA?

2 Answers   UHG,

---

i have completed software testing.Can anyone send sample and simple srs document for writing test cases.

3 Answers   Hexaware,

---

how will you know whether your reported defect rejected?

4 Answers  

---

What Methodology is followed in your testing?

19 Answers   ADP,

---

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.

1 Answers   JWC,

---

Test Documents Reporting answers

4 Answers   ABC, Mastek,

---

Why I think QA is the positon for me

3 Answers  

---

Test summary report detail

2 Answers   Steria, TCS,

---

Hi Friends, Can any one tell me how the Risks for the basic web page testing in the Test Plan, as i am writting my first test plan. It will be greatfull if any one answer me as soon as possible

3 Answers  

---

What is the difference between EXPLORATORY TESTING and ADHOC TESTING?

4 Answers  

---

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 anything else? if require tab is not available then what's the status of test case?

2 Answers  

---

What is the Reporting Tool in java explain and give example?

1 Answers   Wipro,

---