User talk:Smls: Difference between revisions
Content added Content deleted
m (→new test cases for "extract file extension RC task: added responses and other musings.) |
m (→new test cases for "extract file extension RC task: added more comments.) |
||
| Line 55: | Line 55: | ||
: I wouldn't call them incorrect just because they use different examples. Flagging them with the [[Template:Update|needs updating]] template for that would feel a bit harsh, no? Of course, some of the entries might be incorrect because they never read the task carefully, and instead wrote their code around the old examples (which caught fewer edge-cases implied by the task description), or even just read the page title. But that's a problem that many tasks suffer from... :) --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 06:24, 1 September 2016 (UTC) |
: I wouldn't call them incorrect just because they use different examples. Flagging them with the [[Template:Update|needs updating]] template for that would feel a bit harsh, no? Of course, some of the entries might be incorrect because they never read the task carefully, and instead wrote their code around the old examples (which caught fewer edge-cases implied by the task description), or even just read the page title. But that's a problem that many tasks suffer from... :) --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 06:24, 1 September 2016 (UTC) |
||
:: Er, no. It's not they used different <u> examples</u>, but different <u> test cases</u>. That's why they are called ''test cases'', they're to be used to prove (test) that the code works correctly and the test cases are to be used for validation. There's nothing wrong about ''adding'' test cases (of the programmer's choosing, that's done all the time), but the task's test cases are to be used as part of the task's requirements. Otherwise, why have test cases? Test cases are there to have some kind of conformity among the programming entries so as to make them easier to compare. Sometimes, instead of '''test cases''', they are labeled '''examples''', which may or may not be used as part of the task's requirements. This is one reason why test cases are added to instead of replacing them (almost always while the task is still in draft status). -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 17:39, 1 September 2016 (UTC) |
:: Er, no. It's not they used different <u> examples</u>, but different <u> test cases</u>. That's why they are called ''test cases'', they're to be used to prove (test) that the code works correctly and the test cases are to be used for validation. There's nothing wrong about ''adding'' test cases (of the programmer's choosing, that's done all the time), but the task's test cases are to be used as part of the task's requirements. Otherwise, why have test cases? Test cases are there to have some kind of conformity among the programming entries so as to make them easier to compare. Sometimes, instead of '''test cases''', they are labeled '''examples''', which may or may not be used as part of the task's requirements. This is one reason why test cases are added to instead of replacing them (almost always while the task is still in draft status). But I understand your reluctance to flag (almost wholesale) most of the programming entries, but that's the price of changing test cases. It's an easy thing to fix (or accommodate). -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 17:39, 1 September 2016 (UTC) |
||