Changes between Version 23 and Version 24 of MolgenisTicketFaq


Ignore:
Timestamp:
2010-12-01T11:16:22+01:00 (14 years ago)
Author:
Morris Swertz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MolgenisTicketFaq

    v23 v24  
    5858Currently we have four flavors of tickets. For each of them examples are shown:
    5959|----------------
    60 {{{#!td
     60{{{#!td valign="top"
    6161todo
    6262}}}
    63 {{{#!td
     63{{{#!td  valign="top"
    6464A '''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.
    6565So what you need to do is describe this expected output.
    … …  
    7373}}}
    7474|----------------
    75 {{{#!td
     75{{{#!td  valign="top"
    7676enhancement
    7777}}}
    78 {{{#!td
     78{{{#!td  valign="top"
    7979An '''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:
    8080
    … …  
    8686}}}
    8787|----------------
    88 {{{#!td
     88{{{#!td  valign="top"
    8989defect
    9090}}}
    91 {{{#!td
     91{{{#!td  valign="top"
    9292
    9393A '''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.
    … …  
    100100}}}
    101101|----------------
    102 {{{#!td
     102{{{#!td  valign="top"
    103103test
    104104}}}
    105 {{{#!td
     105{{{#!td  valign="top"
    106106A '''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.
    107107