On 1/24/07, Tom Ward <[EMAIL PROTECTED]> wrote: > > On 24/01/07, Anthony Eden <[EMAIL PROTECTED]> wrote: > > > > I know that the issue of closing tickets was brought up a couple of > > days ago and I'm hoping that others might be amniable to a suggestion > > regarding how tickets should be closed. > > > > To me the best way to prepare a ticket for closing is to actually > > either a.) write a unit test which demonstrates that the ticket is not > > applicable > > > or b.) point to a unit test which does the same. To just > > close a report with "works for me" or with "won't fix" seems to be > > dangerous at best, especially when it is a bug report. By going > > through the process of creating a unit test before closing we get the > > benefit of proof, plus the framework gets better test coverage and the > > test can provide the basis for additional tests in the future if more > > information is provided for the issue. > > > > Any thoughts on this? Does this seem like a reasonable thing to do? > > I don't see how a test can be written to show something won't be > fixed. I also don't how a test can prove an issue doesn't exist. > > If tickets are closed with 'works for me', the closer couldn't think > of a test that fails. It doesn't prove the issue doesn't exist, but > then, proving a negative isn't exactly easy. The onus should be on > those with an interest in reopening the ticket to provide a failing > test, rather than on those closing tickets to write passing tests. > > Tom
Agreed - if you don't provide a failing test case with a defect, or at least a very detailed bug report, don't be surprised if it gets closed rather quickly. Thats how open source works - the burden is on the reporter to prove the bug exists as best as possible. - rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
