Explore topic-wise InterviewSolutions in Current Affairs.

A Sample Defect Report Template:

• Defect ID: Unique No or Name
• Description: Summary of the defect
• Feature: Module / Function / Service , in these module TE found the defect
• Test Case Name: Corresponding failing test condition
• Reproducible (Yes / No): Yes -> EVERY time defect appears during test execution

No -> Rarely defect appears

If Yes, attach test procedure:

If No, attach snapshot & strong reasons:

• Status: New / Reopen
• 7) Severity: Seriousness of defect w.r.t FUNCTIONALITY (high / medium / low)
• Priority: Importance of the defect w.r.t customers (high / medium / low)
• Reported BUG: Name of Test Engineer
• Reported on: Date of SUBMISSION
• Assign to: Name of the responsible person in development team -> PM
• Build Version ID: In which build, Test Engineer fount the defect
• Suggested fix (Optional): Tester tries to produce suggestion to solve this defect
• Fixed by: PM or Team Lead
• Resolved by: Developer name
• Resolved on: Date of solving By Developers
• Resolution type: check out in next page
• Approved by: Signature of Project Manager (PM)

Note: Defect Report Template may vary from one COMPANY to another and one project to another

A Sample Defect Report Template:

No -> Rarely defect appears

If Yes, attach test procedure:

If No, attach snapshot & strong reasons:

Note: Defect Report Template may vary from one company to another and one project to another

A document REPORTING on any flaw in a COMPONENT or SYSTEM that can cause the component or system to fail to perform its REQUIRED FUNCTION.

A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.

A procedure to derive and/or select test CASES TARGETED at ONE or more defect categories, with tests being DEVELOPED from what is known about the specific defect CATEGORY.

A procedure to derive and/or select test cases targeted at one or more defect categories, with tests being developed from what is known about the specific defect category.

The number of defects identified in a COMPONENT or system divided by the size of the component or system (EXPRESSED in STANDARD measurement TERMS, e.g. lines-of code, number of CLASSES or function points).

The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g. lines-of code, number of classes or function points).

An OCCURRENCE in which one defect prevents the DETECTION of ANOTHER.

An occurrence in which one defect prevents the detection of another.

DEFECT REPORTING Process:

Defect Reporting Process vary from one COMPANY to ANOTHER.

1. Small scale Company:Tester -> DEVELOPER
2. Medium scale Company:Tester -> Test Lead -> Development Lead -> Developer
3. Large scale Company:Tester -> Test Lead -> DTT -> Development Lead -> Developer

Defect Reporting Process:

Defect Reporting Process vary from one company to another.

The number of DEFECTS found by a TEST phase, divided by the number found by that test phase and any other means AFTERWARDS.

The number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards.

A TOOL that facilitates the recording and STATUS tracking of DEFECTS and changes. They often have workflow-oriented facilities to track and control the allocation, CORRECTION and re-testing of defects and provide reporting facilities.

A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.

The process of recognizing, investigating, taking action and disposing of DEFECTS. It involves recording defects, CLASSIFYING them and identifying the impact.Some companies use Manual Process (EXCEL workbook), and some companies use Tool BASED process for Defect Management.

Tools Examples:Bugzilla / Issue-Tracker / PR-Tracker/Jira / Quality Center etc...(ANYONE)

The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.Some companies use Manual Process (Excel workbook), and some companies use Tool based process for Defect Management.

Tools Examples:Bugzilla / Issue-Tracker / PR-Tracker/Jira / Quality Center etc...(anyone)

DEFECT LIFE CYCLE

Different Flows of the Defect :

• NEW > Opened > Closed
• New > Opened > Closed
• New > Opened > Fixed > Re-Opened > Fixed > Closed
• New > Opened > Deferred
• New > Opened > REJECTED > Re-Opened > Fixed > Closed Etc...

Defect Life Cycle

Different Flows of the Defect :

Status of Defects

New: Tester provides new status while Reporting (for the first time)

Open: Developer / Dev lead /DTT opens the Defect

Rejected: Developer / Dev lead /DTT REJECTS if the defect is invalid or defect is DUPLICATE.

Fixed: Developer provides fixed status after fixing the defect

Deferred: Developer provides this status due to time etc...

Closed: Tester provides closed status after PERFORMING confirmation Testing

Re-open: Tester Re-opens the defect with valid reasons and PROOFS

Status of Defects

New: Tester provides new status while Reporting (for the first time)

Open: Developer / Dev lead /DTT opens the Defect

Rejected: Developer / Dev lead /DTT rejects if the defect is invalid or defect is duplicate.

Fixed: Developer provides fixed status after fixing the defect

Deferred: Developer provides this status due to time etc...

Closed: Tester provides closed status after performing confirmation Testing

Re-open: Tester Re-opens the defect with valid reasons and proofs

If a Defect is some TIME times only appearing then that Defect is not PRODUCIBLE defect, we have to provide PROOF (snap shots or database dumps) for LOCATING it.

If a Defect is some time times only appearing then that Defect is not producible defect, we have to provide proof (snap shots or database dumps) for locating it.

If a Defect is appearing EVERY time (in every EXECUTION) then that Defect is producible defect, we can provide STEPS for LOCATING it.

If a Defect is appearing every time (in every execution) then that Defect is producible defect, we can provide steps for locating it.

TERMINOLOGY vary from one PHASE to ANOTHER in SOFTWARE Application Life Cycle

Software Application Life Cycle has 3 phases;

• Development phase:in Development phase if developers find any mismatch they call it as ERROR or mistake
• Testing phase:In Testing phase if Testers find any mismatch they call it as Defect or Bug or Fault
• Production phase:In Production phase if Customers or End Users find any mismatch they call it as Failure

Terminology vary from one phase to another in Software Application Life Cycle

Software Application Life Cycle has 3 phases;

A FLAW in a component or system that can cause the component or system to fail to PERFORM its required function, e.g. an incorrect STATEMENT or data definition. A defect, if encountered during EXECUTION, may cause a failure of the component or system.

A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.