DMS Training Version: 2.8 Author: Hoang A Na – FRD.BGD Updated by: HuyenLL

1. DMS Training Version: 2.8Author: Hoang A Na – FRD.BGD Updated by: HuyenLL 2014年10月6日(月) Instructor:

2. Introduction • Purpose: Guide project team to understand about defect information, logging, monitoring and measuring defects using Defect Management System (DMS) • Duration: 2 hours • Audience: PM, PTL, Dev, Tester, QA • Test: Paper or online post assessment with pass mark of 25/40

3. Objectives After the course, student will: • Understand basic concept of Defects • Able to use DMS for defect logging/tracking

4. Part 1: CONCEPTS of DEFECT • Defect Concept • Defect information in DMS. • Detail for : • Defect Status • Defect Severity • Defect Type • Cause Category • Defect original

5. What is a defect? • A defect is any non-fulfilment of a product requirement related to an intended or specified use. (All non-fulfilment found by internal reviewer, external reviewer and customer). • Testing activities & Reviewing activities are called “Quality Control activities” (QC activities) • Reviewing activities include: Document review ; code review; other review, acceptance review. • Testing activities include: Unit test, integration test, System test, Other test ,Acceptance test. • If you consider any recommendationsto fix, this recommendation should be logged as a defect in DMS.

6. What should be done after a defect is found? • The defect is logged into DMS. • The defect needs to be communicated and assigned to developers that can fix it. • After the defect is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn’t create defects elsewhere. • DMS should encapsulate these processes.

7. Defect information • The defect information includes Severity, Type, Description…. as below image

8. DEFECT STATUS

9. DEFECT STATUS (cont.) • Error: The defect is not fixed, or fixed but not satisfactorily as required • Assigned: The defect is reviewed by PM/PTL and assigned to one member to fix it • Corrected: The defect is already fixed and waiting to re-test • Closed: The defect is fixed satisfactorily as required • Accepted: The defect has not been fixed satisfactorily as required, but it’s accepted by concession of authority or customer • Cancelled: It’s not a defect or defect is removed by actions other than bug fixing.

10. Defect Severity - FATAL • Defect severity have 4 levels : Fatal, Serious, Medium and Cosmetic with weight 10-5-3-1 . • Fatal • Major errors that cause failure of the application or the building of the application. • Example: • + Misunderstanding major features of customer requirements, that causes rework of whole or major parts of application (for example: main functionalities, application environments, business rules, etc.)    • + Irrecoverable database corruption • +There is no workaround and testing cannot continue

11. Defect Severity - SERIOUS • Serious • Major errors in document s that cause failure in functionalities or failure to achieve quality objectives • Example: • +Do not update related documents (design, test docs) when SRS/design is changed . • +Misunderstanding customer requirements that causes rework of design & coding on 01 or several complicated modules. • + Lack test cases for a module or several modules

12. Defect Severity - MEDIUM • Medium • Minor errors that cause problems during the building of the application or document rework.   • Example: • +Any special cases included invalid data, boundary value,... for major function returns incorrectly    • +Incorrect or old information in reports caused by mistakes    • +Do not have enough or suitable test cases for abnormal cases

13. Defect Severity - COSMETIC • Cosmetic: • Very minor defects, no way to affect the functionalities of the product but still cause rework. • Example: • + A spelling/ grammatical error on a user-interface screen/ message    • + Do not use correct document naming conventions      • + Coding standard: name of object, variables, comments,... 

14. DEFECT TYPE • Defect type is used to group defects by classifying types of problem.

15. DEFECT TYPE - Functionality • Incomplete Function Ex1: Customer request: C = A + ABS(B)                But developer does C = A + B. Ex2: Requirement: Year field accepts value from 1990 to 2020           Dev: Year field accept any number value • Feature missing Ex: Customer requests 3 functions: Add new, modify and delete user.            But developer does only 2 functions: Add new and delete user. • Business logic Ex: In a system: - Page 1: When user click ”Back” button, system displays previous page with status the same user has been done before. - Page 2:  The ”Back” button  system displays previous page but the previous status the same user has been done before was refreshed.

16. DEFECT TYPE – Coding • Coding • Register • Command • Compile • Name/Branch place • Coding standard • Hard Code • Redundancy code • Logic of code • Other Example: For component ListView in VB, ListItem is indexed from 1...n (n = Number of ListItem in ListView).          If developer indexes in code: for i = 0 to n-1     ==> The index n is missed, should start with 1. It’s Coding logic defect: "Index of out bound"

17. DEFECT TYPE – User Interface • User Interface • Layout • Label/Massage • Position/size • Examples: - A spelling/ grammatical error on screen/ message     - Align text, fields, forms, labels     - Incorrect Tab index, set default button, set default cursor, short key.

18. DEFECT TYPE - Design issue & Document • Design issue: • Logic Deployment From Function • Data flow • Interface Between Modules • Table Design • Domain Design. • Ex: Lack of the table in design • Document • Grammar • Format/Template • Documentation • Example: • Didn't document correctly while grammatical still right (use wrong words, sentences used not described the correct purposes) …

19. DEFECT Cause Category This field is used to group defect cause by classifying types of problem.

20. Defect Origin Defect Origin indicates the actual process that caused the defect. .

21. Practices • 1.Who are involved in defect fixing process? • 2. Do you need to log a defect found while debugging your code as a unit test defect? • 3. Which is cheaper, preventing defects or fixing them? • 4. What should be primarily based on then scheduling bug fixes?

22. Part 2: DMS FUNCTIONS • Introduction DMS • Actor and Rights • Responsibility • DMS Main Functions. • DMS overview • Manage view • Log defect • Defect report • Import & Export defect. • Others

23. What is DMS use for? • Track project defects on each project work products and modules • Report defects and defect status of project • Follow up defects status • To evaluate quality-related performance of PROJECT or PROCESS NOT INDIVIDUAL through project (or process) metrics collected such as Test effectiveness, Review effectiveness, defect rate, Test effecticy… • Wrong data leads to wrong decision Path to access: http://fsoft-fms/dms2

24. Actors & Rights The Actors • QA • PM/PTL • Tester • Developer Rights: • Submit new defects • View and update defects • View the history of a defect • Update several fields of some defects at the same time. • View defect reports • Only QA Group, QAHO and Admin can delete defect(defects).

25. Rights • QA: • Has permission in Defect Management • All the rights as Tester at project level. • QA can login to all projects that QA dedicated this group. • QA can delete defect of the project. • PM/PTL: • Has permission in Defect Management • Manage Defect and plan defects for WPs, Module • Select the workflow that apply for the project. • Cancelled / accepted the defect. • Tester: • Has permission in Defect Management • Update/change status of the defect in DMS. • Cannot change defect status to “Accepted” • Developer: • Has permission in Defect Management. • Cannot change defect status to “Closed” or “Accepted”

26. Responsibility • QA • Check/ tracking and update defects of all projects. • PM/Project Technical Leader: • Assign users with position to the project (FSoft Insight tool) • Define WPs, Modules of the project (Define in Fsoft Insight tools) • Plan defects for each WP, Module and QC activity (In Fsoft Insight tools) • Select the workflow that apply for the project. • Review new defects, analyze defect origin, defect type, severity and update this fields correctly • Assign a developer to fix it, and change defect status to “Assigned” • Change defect status to “Accepted” or “Cancelled “ in case of concession • Review test result and make causal analysis about defect trends

27. Responsibility (cont.) • Tester • Submit a defect with “Error” status • Track defect status, if it’s “Corrected” re-test the defect • Change status to “Closed” if fixed defect is correct, else to “Assigned” • Report test results before Final inspection: Successful Test coverage • Developer • Fix defects which are assigned to him • Change defect status to “Corrected” afterfixing it

28. DMS Overview

29. Manage views • List of • All defects • All open defects: defects with status • ERROR + ASSIGNED +CORRECTED • All leakage defects: defects of QC activities • Acceptance test • Acceptance review

30. Log Defect • You click on “Add new” button in the screen for logging the defect. • The information defect is OK at least when the mandatory fields are filled up as below image.

31. Defect Report • Report function is used to analyze and evaluate defects of project basing on defect status, defect severity…, and moreover it helps manager to check progress of each Tester and Developer, … • Defect report list in DMS as below image:

32. Defect Report • To view the defect report : Pls. enter information related to report in each filter: From Date/ To Date/ Product Type/ Product /Report Type field then click on the button “Report”. • Ex: The Defect Distribution report

33. Defect Distribution report

34. Import defect • DMS supports Import defect function by an excel template file to log defect. • To download Excel file template : Pls. click on “Download Template file” button as the below image. • Note: • All mandatory fields are in Red and user needs to fill in right format • If any defect lacks information in mandatory fields in Excel file  The defect will not be imported into DMS

35. Exportdefect • To export the defect report. Pls. enter information related to report in each filter: From Date/ To Date/ Product Type/ Product /Report Type field then click on “Export”button as the below image.

36. Exportdefect • To export the defect :Pls. enter information related to defect in each filter: Assigned To/ Status/ QC activity/ Product Type/ …then click on “Search” button as the below image.

37. Exportdefect -> pls. click on Export button.

38. Other features • Move defects • Only QA can perform this task. Should be carefully by moving defects • Step1 :Select defects which should be moved to other project • Step 2:Select the new project from the list • Step3: Click “MoveDefect” button, selected defects are moved to new project. The information of moved defects is kept in new project • Queries • Fix Queries: provided by application • Public Queries: only PM/PTL can create and manage these queries • Private Queries: Each project member can create and manage his queries • Batch Update: the user choose to change status /severity / product type ….of many defects at the same time

39. Practices Log defects in DMS for the cases: 1. In integration test you have to integrated module A with module B. There is a function (XYZ) cannot perform. The cause is the modules B was blocked some command lines Developer of module B forgot to check in latest version (that unblock the command lines) in integration test environments. 2. When customer feedback about the deliver application bugs following: "When Time out occurs. The login dialog is displayed. User inserts incorrect password, Click tab then press OK. Error message is displayed "Error occurs" “ 3. When deploying product on customer’s production environment, you find some errors. How do you log these bugs?

40. Resources & references • Resources • Test Guideline • DMS Guideline • Process_Correction • Recommended readings • DMS help

41. Questions and Answers