On Tue, 2007-05-01 at 15:08 +0200, Piotr Jaroszyński wrote: > Hello, > > There was some discussion about forcing/not forcing tests in EAPI-1, but > there > was clearly no compromise. Imho, tests are very important and thus I want to > discuss them a little more, but in more sensible fashion. > > Firstly each test can be(not all categories are mutually exclusive): > - not existant > - non-functional > - not runnable from ebuild > - useful but unreasonable resource-wise > - useful and reasonable resource-wise > - necessary > - known to partially fail but with a way of skipping failing tests > - known to partially fail but with no easy way of skipping failing tests > Is that list comprehensive? > > Secondly we must answer the question how precisely we want to distinguish > them, so users/dev can choose which categories of tests they want to run. > What comes to mind is: > - run all tests > - run only necessary tests > - run only reasonable tests > - don't run tests at all > Again, is that list comprehensive? >
Don't forget tests that have heavy requirements to run. Many gnome tests, for example, need a virtual X to run, which puts a new set of DEPENDS requirements on your system. Daniel -- [EMAIL PROTECTED] mailing list
