Answer / guest

Defect ID, description, build version ID, feature/module,
test case title that failed, reproducible or not, status
(new/reopen/close), severity, priority, testers name,
reviewers name, date of defect detection, name of developer
assigned to, suggested fix (solution).

Answer / sowjanya

In addition we also have Attachments, History,Reason, area, iteration etc

Hello friends.. Can anybody here explain me or provides me notes of these topics in detail with interview questions... Topics are:- History of Software Engineering Waterfall Model Prototype Model Spiral Model Software Quality Testing Software Development Life Cycle Software Testing Life Cycle white box testing methodology black box grey box Definition of Quality,Quality Assurance,Quality Control Verification and Validation Static Testing Dynamic Testing only on my gmail mca.rachna21@gmail.com

1 Answers  

---

differentiate defect age & build version control?

2 Answers  

---

Test summary report detail

2 Answers   Steria, TCS,

---

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

3 Answers   Hexaware,

---

HI, TRM(Test Responsibility Matrix) and RTM(requirement Tracebility matrix) both are same??

4 Answers  

---

what methods will you follow to repare test cases in your organization?

3 Answers   CTS,

---

Can someone give checklist to test the performance of application. This checklist to be provided in the Test Plan that the following will be tested, e.g. 1. n users will be tested to test the load 2. Per page load time would not be greater than n seconds etc. I want to know the points other than the above stated ones.

0 Answers  

---

how will you know whether your reported defect rejected?

4 Answers  

---

Need information on Documentum4.3, any websites. What is this Documentum,how to access,features and benefits. ASAP Thx.

1 Answers   Cap Gemini,

---

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,

---

Can't we write test plan without any document with us or we definitely require the document for that

5 Answers   ABC, Excel,

---

What is Defect/Bug/Error Life Cycle?

11 Answers   Covansys, Hewitt,

---