Test Reporting: Comaparision of actual value with the expected value. Mismatches are reported as defects.

Defect are errors, issue or bugs program is detected with a problem is an error. The tester detected a problem in build then it is defect or issue. defect reported is accepted to resolve is bug. ****Buggy - program with more no of bugs debugging - the process of finding the cause of the bugs is debugging bebugging - the process of intentionally injecting the bugs. Defect Classification: Severity: Critical, Major, Minor, Trivial (s1, s2,s3,s4) ( Probability: visibiliy of that defect, High , medium, low (Usae of the feature) priority: importance and urgency of fixing the defect. , HIGH , Medium, Low (P1, p2, p3) Related module:, Module 1, Module 2, Module 3 Phase Detected: unit testing, integration, system testing, UAT Phase injected: Req's development, HLD, Coding, BUild

Defect Report: Defect ID: Unique identifier for future references, Project Name: Project Code: Sumary: Feature / Functionality: Test Case Name: Reproducible: defect repeatability during the test execution for many times YEs: It is reproducable, attach test procedure NO: It is not reproducable. We take screenshot attach along with the test proced ure.

Status: New, Reopen Severity: PRiority: Assigned to: Name of the developer Detected by: Reported on : Build Version ID: Suggested to fix:

BY Developers: Fixed by: Resolved o: Resolution type: Approved by:

Types of Defects: 1. User Interface: Low severity: allignment (Low Priority) Spelling mistakes (High Priority), improper

2. Input domain: medium severity, valid inputs are not taken (Hihg Priority), 3. error handling: Medium severity, no error message is displayed for wrong ope ration (High Priority), Complex error message (Low PrioritO) 4. calculation: High Severity, Wrong Inputs (High Priority) 5. load conditional: High Severity build is not supporting more than one user ( high Priority), Low Priority, Meduim priority 6. hardware defects: High Severity, Build not supporting any of the hardware d evices (High Priority), wrong output from hardware 7. version control system: High Severity: Mistakes in the version control 8. source defects: Mistakes in the help document

Defect Life Cycle:

Bug Life Cycle: journey off a bug from its identification to its closure. BUG STATUS: NEW OPEN - ASSIGNED DEFERRED - decided to fix it in the upcoming releases instead of the current rel ease DROPPED - REJECTED FIXED - RESOLVED - COMPLETED REASSIGNED - REOPEN CLOSED - VERIFIED Reporting defects effectively: Be specific: BE detailed: Be objective: reproduce the defect: Review the report:

Defect Age: the difference between the date of the defect identified and the cu rrent date / date of defect fixed (Time & Phases) Defect Density: Number of defects / size Defect Detection efficiency: no of defects identified / no of defects injected

Test Closure: Test lead will submit the test summary report to the project manager. No of test scenarios, use cases, No of test cases, test cases executed

defects identified Defects fixed Defects deffered Defect fixation percetage: Comments, Remarks; Test closure summary Report: Reviewed & Approved: