On Wed, Aug 29, 2012 at 3:44 AM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > > I suppose you could see it as a semantic nuance. However, to my mind, > there is a different. A skipped test is something that could -- or > even *should* be run -- but can't due to missing some optional > prerequisite. In this case, we're talking about tests that can't ever > be run. To my mind, it doesn't make sense to have those tests present > but "skipped".
I'm not sure I see the difference between a configuration that makes a test unnecessary and a missing optional dependency that makes a test unnecessary. In both cases a skipped test means roughly, "A test was found, but due to the particulars of your environment it doesn't make sense to run it." Django users trying to validate a django deployment can and should ignore both kinds of skipped tests. Core developers cutting a release should investigate both kinds of skipped tests, because it means the test coverage wasn't 100%. Since a skipped test signals the roughly the same thing no matter the cause, there's little reason to differentiate them. Best, Alex -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
