Sunday, December 31, 2006

HOMEWORK -2: WEEK: 3

Question 7. Have you attended Walkthrough meeting? What is done in Walkthrough meetings?
Question 8.
What are different STATUS in a defect? Explain.


9 comments:

subash singh said...
This comment has been removed by a blog administrator.
subash singh said...
This comment has been removed by a blog administrator.
subash singh said...

By: Subash Singh
1. Have you attended the walkthrough meeting? What is done on the walkthrough meeting?

Ans: Yes, I have attended the walkthough meetings. In a walkthrough meeting business analyst or business managers does the presentation on requirement document or design document. The purpose of the walkthrough meeting is to familiarize the testing or developer team with fucntions and feature of the application that is being developed. It is also the medium of knowledge sharing, communicating and feeding inputs among Testers, Developers and the Management Team.

2. What are the different status of a Defect? Explain

Ans: The different status are:
Critical: Critical are those defects which includes unusable functions or links, causes general protection fault or the fucntion of the module causes problem elsewhere.

High: Fucntions that does not perform as required by the Design or Requirement Document.

Medium: Function that performs as the requirement of BRD but not quickly as expected or does not meet the standards and conventions.

Low: This kind of defect is not critical to the system. It includes error like color mismatch, spelling errors or irrelevent error messages etc

Unknown said...

Murari Naral 01/01/2007

7. Have you attended Walkthrough meeting? What is done in Walkthrough meetings?

Yes, I have attended Walkthrough meeting. In this meeting the Business Analyst describes the requirement document step by step, page by page to make other members involved in the project understand the module/application/functionalities to be designed. A walkthrough meeting can be ivited by anyone if something important is to be described among the members of the project.

8. What are different STATUS in a defect? Explain

Defects status can be catagorised in 4 levels.
1. New: A newly originated defect which has been put forward for research and solution.
2. Assigned: A defect which has been asigned to a developer to investigate and fix the problem.
3. Resolved: A defect which has been worked out and problem has been fixed by the developer but still open to retest by the tester.
4. Closed/Reopen. The "Closed" status defect is the defect which is closed by the tester after performing retesting on it whereas the "Reopen" status defect is the defect which is worked by the developer with a "Resolved" status but the defect still remains while testing is done by the tester. So the defect is reopened with "Reopen" status.

ngopes said...

gopes 01/02/2007

Question 7. Have you attended Walkthrough meeting? What is done in Walkthrough meetings?
Yes I have attented walktrough meeting.
A walkthrough meeting is a meeting, in which the Business Analysts describe the requirement documents step by step, page by page to make the other members of the team understand how the module or application or functionalities are designed. This is a kind of a refresher class for the testers.
Question 8. What are different STATUS in a defect? Explain.
The different status of defect are:
1. New/submitted: This is a new found defect and submitted(logged) to fix the defect.

2. Assigned: Defect that is assigned by the developer to fix to the individual responsibe for that module
3. Resolved: The defect that has been solved by the developer, but still remain to test by the tester.

4. Closed Reopen: The defect that is passed and closed by the tester after retesting the application..whereas reopen is the defect worked by the developer..but the defetc still remain and the defect is in reopen status.
Question 3. Once you find a defect, what do you do?
Once I find a defect i try to recreat the defect


Question 5. What different types of jobs have you done in TestDirector?
As a tester i have :
Logged the defect
written test plans
written test cases
mapped the requirements to the test cases
generated defect reports


Question 6. What are different levels of severity of a Defect?
The different level are
Critical defect: SYstem doesnot work as we open our assigned module.
High: Donot match with the Requirement doc.(RD)

Medium: the display page doesnot match with the RD

Low: Negligible errors like clolr size of the text etc.

Anonymous said...

Yuba R Dhakal 01/03/07

1. Have you attended walk through meeting? What is done in walkthrough meeting?

Yes, I have attended several walkthrough meetings.
In a walkthrough meeting, most of the cases the Business Analysts describes the over all project and requirement documents step by step, page by page to make the other members of the team understand how the module or application or functionalities are designed.

2. What are the different statuses in a defect? Explain.

There are four different statuses in a defect.
New/ Submitted: When testers test the application and found the defect in the application then he log the defect, it is called new or submitted.

Assigned: When tester submitted the defect then it has to be assigned to developer to fix the problem, then the status of defect called assigned.

Resolved: When the defect assigned to the developer and he fix the problem, then the defect would be in assigned status.

Close/ Reopen: When the developer fixes the problem in the application then it will come back to the testers to re-test. When tester re-tests that part of defect then if it were fixed, he closes the defect and if not fixed or still remain the defect, then he reopens the defect.

subash singh said...

By: Subash Singh
This is the correction to my previous answer.

What are the different status of Defect? Explain.

Different status of defects are as follows:
New/Submitted: This is newly submitted or logged defect. At present no further action has been taken for this kind of defect.
Assigned: It is the defect which has been assigned to respective developer for bug fix.
Resolved: When the developer fixes the defect it is categorize as Resolved by the developer himself.
Close/Reopen: After the bug fix testers retest the application to verify whether the defect exists or not. If the defect is fixed it is put into Close or else into Reopen status.

subash singh said...

Please make correction to my answer number 2. Consider this answer for: What are the different level of Defect?

QA Questions said...

Rajan Bhandary


Question 7. Have you attended Walkthrough meeting? What is done in Walkthrough meetings?

I have attended walkthrough meeting. In a walkthrough meeting, where business analyst describes each and every functions of the application page-by-page to the Developer Team, CMT, QA team and other people who are going to involve in that project. Basically, it is a presantation done by Business Analyts as per Requirement Document.

Question 8. What are different STATUS in a defect? Explain.

New: Initial stage when a defect is added.
Assigned: Once the defect is added, It will assign to developer.
Resolved: Once the developer refix the defect, the status of defect will be resolved.
Closed/Reopen: QA will retest the defect several times if there is no defect, QA will close the case otherwise He/she will reopen again.