Defect Life Cycle:
When tester find defect then tester will raise or log defect in defect management tool like QC,Bugzilla, Test director with the status as New then developer will change the status to Open and validate the defect, if defect is valid then change status to Assign and then Fix the defect and change the defect status to Fixed. Then when ever new build deployed developer will change the defect status from Fixed to retest and assigned to respect Tester. Then tester will retest the defect if it is working fine then close the defect if not working properly then reopens the defect and assigned back to Developer.This is completely positive flow. The other flow in Defect Life Cycle is if defect rejects then there are 3 reasons to reject the Defect 1. Reject Not reproducible: Developer try to reproduce the defect then if he is not able to reproduce the defect then developer will re-assign defect to Tester by changing the defect status to "Reject Not Reproducible" 2. Reject Working as Per requirement: developer validate the defect then if it is working as per the requirement he will resign defect to the tester by changing the status as "Reject Working as per Requirement". 3. Reject Invalid: Developer validate the defect then he will reject the defect due to other reasons like Environmental Issues, Tester don't know to test that requirement, particular functionality not yet developed, etc,. 4. Differ: If particular defect required to change the requirement and that requires BA (Business Analyst) approval to fix that particular issue and also that cannot implement with current module or iteration to fix that then developer change the status to Differ and assigned to Business Analyst. Software Testing Methodologies Below are few commonly used software testing methodologies:
Software Testing Concepts Acceptance testing: Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component. Ad hoc testing: Ad hoc testing carried out using no recognized test case design technique. Alpha testing: Alpha Testing simulated or actual operational testing at an in-house site not otherwise involved with the software developers. Backus-Naur form: Backus-Naur form is a metalanguage used to formally describe the syntax of a language. Beta testing: Beta testing is Operational testing at a site not otherwise involved with the software developers. Big-bang testing: Big bang testing is part of Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
0 Comments
Leave a Reply. |
|