Not just before release, but just before merging pull request into master too. That means there is room for an error here and there. Why create that error? Just because everyone running all tests could read their e-mail for minute or two?
I'd still suggest not make any distinctions between tests. This just creates confusion to everyone (to me, to you, to possible contributors and so on) and a room for errors. People tend to forget and make mistakes. Why even create that additional possibility when there's enough of these? As i said, when someone is dealing with some specific thing then he/she can run only the specific tests and ignore anything else. Jarmo On Tue, Jan 11, 2011 at 4:48 AM, Bret Pettichord <b...@pettichord.com>wrote: > I think it would be great to create a new rake target that runs all the > unit tests that should be run before a release. > > Bret > > On Mon, Jan 10, 2011 at 3:44 AM, Jarmo <jarm...@gmail.com> wrote: > >> Replying here to http://jira.openqa.org/browse/WTR-472 to avoid offtopic >> on JIRA: >> >> Bret wrote: >> >> >> Is there also any reason why window_tests are not included into >> core_tests? That's one of the reasons why the problem didn't come out before >> the release. >> >> > The reason is simply that the window_tests take over your desktop, so >> you can't do anything else while you are running the tests. Whereas the >> core_tests do not, so you can check email or whatever while you > are >> running them. >> >> > Perhaps we need a standard checklist of tests we should run before a >> release so we don't miss something like this again? >> >> I think we shouldn't make any distinction between tests, but should run >> all tests with `rake test`, that's because all manual intervention causes >> problems like just happened. I don't think that these tests interfere too >> much while running, especially since they're not ran 24/7 on your desktop, >> but right before needed. My suggestion would be to include all tests into >> `rake test` or delete the tests which are not run. The less distinctions, >> the better. >> >> > I agree that this warrants a 1.7.1 release ASAP. >> >> Done. >> >> >> Jarmo >> >> _______________________________________________ >> Wtr-development mailing list >> Wtr-development@rubyforge.org >> http://rubyforge.org/mailman/listinfo/wtr-development >> > > > > -- > Bret Pettichord > Director, Watir Project, www.watir.com > > Blog, www.testingwithvision.com > Twitter, www.twitter.com/bpettichord > > > _______________________________________________ > Wtr-development mailing list > Wtr-development@rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list Wtr-development@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development
