Presentation is loading. Please wait.

Presentation is loading. Please wait.

Error and Defect Management in context of IFDK reference product.

Similar presentations


Presentation on theme: "Error and Defect Management in context of IFDK reference product."— Presentation transcript:

1

2 Error and Defect Management in context of IFDK reference product

3 About this course material -This material if for general training for Error and Defect Management -Material is more supportive in class room -Material will be updated during courses -FreeNest Portable Project Platform is used to demonstrate things only in practice. This is not limiting usage for material for other training environments (I hope ) About material

4 Definitions Failure - Fault, Defect, Bug - Incident, Failure, Error Example forum thread: http://www.allinterview.com/showanswers/36257.htmlhttp://www.allinterview.com/showanswers/36257.html ISTQB syllabus Yläotsikko

5 Customer/Business Requirements Sub System Requirements Component Requirements Component / Unit Testing Integration Testing System Testing Acceptance Testing System Requirements Architecture& Design& Implementatio n Product VALIDATION VERIFICATION Error Database Error Database MAINTENANCE Error Database & Management covers whole product life cycle PRODUCT END timelinetimeline

6 ● TEST CASE ID XXXXX ● Step1 ● Step2 ● Step3. ● Step4. ● TEST CASE ID XXXXX ● Step1 ● Step2 ● Step3. ● Step4. INCIDENTS Bug/Defect Report Bug/Defect Report Error Database System Under Test EXECUTE TEST ! Test Engineer Writes report and provides evidences What means error/defect reporting? Yläotsikko Collects INCIDENTS Can lead to

7 Example Sources for error report CRM Field Testing Testing Process Customer Feedback / Customer Feedback / Error Report Change Request? Change Request? N x Incidents Yläotsikko

8 ● Defect/Burg/Error ID ● Reporter ● Time ● Founded where ● Which way? ● Test Case ● Test Setup/Configuration ● Describe scenario? ● Attachements? Picture/Log/etc.. ● Defect/Burg/Error ID ● Reporter ● Time ● Founded where ● Which way? ● Test Case ● Test Setup/Configuration ● Describe scenario? ● Attachements? Picture/Log/etc.. Error Database Error Database Id1 Id2 Id1 Id3 Id1 Error/Bug/Defect Report

9 Id1 Id2 Id4 Id3 Nature of bug? Location? Priority? Severity? Where is the bug is found?Which one should fixed first? How fatal is the bug? Id2 ID N Target? When the bug should be fixed and verified ?

10 Testing Levels and Error Management UNIT TESTING – Developer's area Implementation Test Framework Error Database Error Database

11 Integration Testing Implementa tion Test Framework Error Database Error Database Test Plan Test Plan Implementa tion Test Framework Component 2

12 System & Acceptace Testing Implem entati on Test Framewo rk Error Database Error Database Te st Pl an Te st Pl an Implem entati on Test Framewo rk Component 2 Test Plan Test Plan IFDK HARDWARE DESIGN IFDK HARDWARE DESIGN IFDK HARDWARE PROTOTYPE VERIFICATED IFDK HARDWARE PROTOTYPE VERIFICATED

13 Error/defect life cycle Yläotsikko

14 Error fixing and release Week 0 Week 26 Week 52 REL 0.1 REL 0.2 REL 0.5 REL 1.0 Defect Found Defects Found Future ?

15 Hands On: Bugzilla Error Database http://www.bugzilla.org/ http://www.bugzilla.org/installat ion-list/ http://www.bugzilla.org/ http://www.bugzilla.org/installat ion-list/ What is Bugzilla? Bugzilla is a "Defect Tracking System" or "Bug-Tracking System". Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favorite of thousands of organizations across the globe. What is Bugzilla? Bugzilla is a "Defect Tracking System" or "Bug-Tracking System". Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favorite of thousands of organizations across the globe.

16 Reporting, Metrics and daily usage

17 Bugzilla Yläotsikko

18 Other Defect Database Solutions JIRA – Commercial Requisite Pro – Commercial Rational Synergy - Commercial Mantis – Open Source

19 Testlink and Bugzilla Test Management Database Test Management Database Feature Implementation Feature Implementation TestCase Bug Report Error Database Error Database PASS FAIL TestCase Test Plan/Suite SourceCode Version Control SourceCode Version Control BUGZILLA TESTLINK VC + Implementation

20 Feature or Bug? That's a question!

21 Yläotsikko

22 Change Management Sometimes founded defect can lead to change Bug? Change Request? Not Clear Requirements Not Clear Requirements Feature ? Yläotsikko

23 Traditional SW Project vs Open Source Project Open Source – Crowd Sourcing SW Relase tested without coordination by group of volunteers Release tested by customer Field Testing Test Group Yläotsikko


Download ppt "Error and Defect Management in context of IFDK reference product."

Similar presentations


Ads by Google