Changes between Version 7 and Version 8 of MolgenisTicketFaq
- Timestamp:
- 2010-12-01T10:31:55+01:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MolgenisTicketFaq
v7 v8 49 49 == Ticket types == 50 50 51 Currently we have four flavors of tickets: 51 Currently we have four flavors of tickets. For each of them examples are shown: 52 |---------------- 53 {{{#!td 54 todo 55 }}} 56 {{{#!td 57 A todo is a unit of work that does not result in commits to SVN but instead in a wiki page, Excel document, a presentation and so on. 58 So what you need to do is describe this expected output. 52 59 53 === defect === 54 A defect is a known error in our code base. Therefore the ticket MUST describe what you need to do to reproduce the defect. 55 ExpeIf possible you will first create a UnitTest that shows the bug so that it can never come back without us knowing. 60 Example ticket: 56 61 57 62 {{{ 58 To reproduce the defect: 63 Why or for whom? 64 For medgen and bbmri we want to compare imputation methods Beagle, Impute and MACH. 65 66 Expected output? 67 An Excel document that describes a comparable percentage correctly estimated SNPs. 68 69 Action plan? 70 Take existing genotype data from 1M arrays and split the data randomly in two. The first half we input into the impute methods. Then we compare the SNPs called with those actually called on the array and calculate percentage correctly estimated SNPs. 71 72 Evaluation plan? 73 We will feed back results to Lude and Cisca's teams to evaluate outcomes and if necessary propose further testing. 74 }}} 75 76 }}} 77 |---------------- 78 {{{#!td 79 defect 80 }}} 81 {{{#!td 82 83 A '''defect''' is a known error in our code base. In this case the ticket MUST describe what you need to do to reproduce the defect. If possible you will first create a UnitTest that shows the bug so that it can never come back without us knowing. 84 85 Example ticket: 86 {{{ 87 88 Why or for whom? 89 This ticket is a showstopper for ticket #1 in COL7A1 90 91 Expected output? 59 92 1. checkout molgenis and molgenis_test 60 93 2. generate code 61 3. run handwritten/tests/TestThisBug.java 94 3. run handwritten/tests/TestThisBug.java without errors 62 95 63 The error log is as follows: 96 Action plan? 97 The current error log is as follows: 64 98 <paste of error log> 99 100 Evaluation plan? 101 run handwritten/tests/TestThisBug.java without errors 65 102 66 103 }}} 67 104 68 === Enhancement === 105 }}} 106 |---------------- 107 {{{#!td 108 test 109 }}} 110 {{{#!td 111 A '''test''' is a special ticket to move the todo of 'testing' an enhancement or bugfix to others in the team. Usually it only refers to the other ticket where the actual bug/enhancement is described. Also newly reported bugs may first need a test case before the tickets can be changed into a bugfix. 112 }}} 69 113 70 114 71 '''todo''' - these are actions that don't produce code but something else. For example: an excel with quality scores for each NGS lane.72 115 73