Re: Tests, Emacs-25 and Conditional Features

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Date: Fri, 18 Mar 2016 17:19:22 +0000
> Cc: Eli Zaretskii <address@hidden>, address@hidden
> 
> Michael Albinus <address@hidden> writes:
> 
> > address@hidden (Phillip Lord) writes:
> >
> > Hi Philip,
> >
> >> Something like
> >>
> >> (skip-unless (or (gnutls-available-p) conditional-feature-force))
> >>
> >> So, we pick have a standard test selector which means "all the
> >> conditional features should be expected to be on". Probably, you would
> >> want "all the conditional features that are supposed to be on by
> >> default, should be expected to be on"
> >
> > That does not exist for everything. For example, in the file
> > notification case there are 5 different possible "conditional features",
> > all of them valid:
> >
> > - inotify enabled
> > - kqueue enabled
> > - gfilenotify enabled
> > - w32notify enable
> > - file notification disabled.
> >
> > How does a test library shall know what is intended by the user?
> 
> Good point, although, if I understand the notification correctly, you
> have an abstraction layer over these?

The abstraction layer is not relevant if you want to test the
low-level functionality.