Содержание
- 2. Definitions Why do we need defect reports? Defect Life Cycle Defect Report Defect Reporting Tips Defect
- 3. Definitions Mistake (Error) - human action that produces incorrect result Defect (Bug, Fault) - a flaw
- 4. Definitions Defect Report - a document reporting on any flaw in a component or system that
- 5. Why do we need Defect reports? To provide programmers, managers and others with detailed information about
- 6. Defect Life Cycle In Progress Detection Reporting Fixing Retesting Closure Assigning Failed Verification Not An Issue
- 7. Test Incident Report (Defect Report) According to IEEE 829 Test Incident Report consists of: Test Incident
- 8. Severity and Priority Severity – the degree of impact that a defect has on the development
- 9. Try to reproduce symptoms when you see them Try to isolate the defect by making carefully
- 10. Defect Tracking Tool - a tool that facilitates the recording and status tracking of defects and
- 11. Defect Tracking Tools Collect defect/request records Assign defect/request record to the responsible person Collect defect/request history
- 12. Defect Tracking Tool Defect Reporting 1. Click Create Issue
- 13. Defect Tracking Tool 2. Select ‘Issue type’ = “Bug” 3. Set short and clear Summary
- 14. Defect Tracking Tool 4. Select Priority* of the defect 5. Select component, where you’ve found the
- 15. Defect Tracking Tool 6. Put down Description, Steps, Actual and Expected results into Description field 7.
- 16. Defect Tracking Tool Defect filtering Use configurable filter to find defect by its parameter Use quick
- 17. Defect Tracking Tool Other features Use link icon to get permanent link of your unsaved filter
- 19. Скачать презентацию