On 1/24/07, Tom Ward <[EMAIL PROTECTED]> wrote: > > 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.
A passing test case which demonstrates that specific input results in specific output indicates that an issue doesn't exist, at least using the assumptions of the original issue. Granted a test case may pass in one case and fail in another due to variations in the environment (OSes, configurations, etc) however a test is better than no test. As for test cases for something which won't be fixed, at least point to or provide a test case which demonstrates the expected behavior. If there is no test case then the correct behavior is a matter of interpretation and will often lead to confusion, bugs, more people raising issues, etc. > 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. How do you know that the closer couldn't think of a test that fails? Unless the closer creates a test that passes based on a set of assumptions then how do you know what lead them to believe that it works for them? We don't know what the closer's assumptions were, and the point of test cases is to define something which can be applied repeatedly with the same assumptions and which results in the same outcome. I think if an issue can be legitimately closed with a passing test case then the onus does reasonably shift to the original person who wrote the ticket to provide a test case that fails. V/r Anthony Eden -- Cell: 808 782-5046 Current Location: Melbourne, FL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
