Changes between Version 8 and Version 9 of MolgenisTicketFaq
- Timestamp:
- 2010-12-01T10:42:34+01:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MolgenisTicketFaq
v8 v9 55 55 }}} 56 56 {{{#!td 57 A todois 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.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 58 So what you need to do is describe this expected output. 59 59 60 Example ticket: 60 Example ticket: '''Comparison of imputation methods Beagle, Impute and MACH''' 61 61 62 62 {{{ 63 component: gwas 64 63 65 Why or for whom? 64 66 For medgen and bbmri we want to compare imputation methods Beagle, Impute and MACH. … … 77 79 |---------------- 78 80 {{{#!td 81 enhancement 82 }}} 83 {{{#!td 84 An '''enhancement''' is working on a new set of features in our software. In this case we EXPECT that there has already been a ticket that defines this enhancement. In these cases the ticket is simple: 85 86 Example ticket: Implement use case: SearchQTLprofiles 87 {{{ 88 component: xqtl 89 90 Implement the enhancement as described in 91 92 http://www.xgap.org/wiki/XqtlReview#Usecase1.SearchQTLprofiles 93 }}} 94 95 }}} 96 |---------------- 97 {{{#!td 79 98 defect 80 99 }}} 81 100 {{{#!td 82 101 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.102 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 and you MUST create a test that shows the problem. If possible you will first create a UnitTest that shows the bug so that it can never come back without us knowing. 84 103 85 Example ticket: 104 Example ticket: Fix JPA if primary key is not named 'id' 86 105 {{{ 106 component: molgenis 87 107 88 108 Why or for whom? 89 This ticket is a showstopper for ticket #1 in COL7A1109 This ticket is a showstopper for ticket xyz. 90 110 91 111 Expected output? 92 112 1. checkout molgenis and molgenis_test 113 2. add a new <entity> with a <field name="myid" type="autoid"/> 93 114 2. generate code 94 3. run handwritten/tests/TestThisBug.javawithout errors115 3. run build.xml without errors 95 116 96 117 Action plan? 97 The current error log is as follows: 98 <paste of error log> 118 Correct generators to get rid of compile errors. 99 119 100 Evaluation plan?101 run handwritten/tests/TestThisBug.java without errors 120 Evaluation method? 121 UnitTest. If it is a user interface error you have to describe the procedure here. 102 122 103 123 }}} … … 110 130 {{{#!td 111 131 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. 132 133 Example ticket: 134 {{{ 135 Why or for whom? 136 We got a report stating that the REST api doesn't work from Java client 137 138 Expected output? 139 Have a test case that uses the REST api and succeeded/fails 140 141 Action plan? 142 Create a small REST client 143 144 Evaluation method? 145 Feed back to the bug reporter what we found and what actions we will take. 146 }}} 147 112 148 }}} 113 149
