Re: Techniques to detect API/ABI changes



As I said, it's a new GUnit suite (reusing tests) that link against
libraries installed on the system (for example the previous release
when you have that). The selection of tests in the suit are more
limited (only public) so that you can see which ones actually break
the external API.

2006/11/26, Philip Van Hoof <spam pvanhoof be>:
But then, what does the new test actually test?

On Sun, 2006-11-26 at 23:38 +0100, Øystein Gisnås wrote:
> Those files are already there.. Existing tests..
>
> 2006/11/26, Philip Van Hoof <spam pvanhoof be>:
> > You didn't add those files to the attachments of your E-mail
> >
> > On Sun, 2006-11-26 at 23:20 +0100, Øystein Gisnås wrote:
> > >  tny-api-test-suite.c \
> > > +       tny-list-test.c \
> > > +       tny-device-test.c \
> > > +       tny-account-test.c \
> > > +       tny-folder-test.c \
> > > +       tny-mime-part-test.c \
> > > +       tny-test-stream.c \
> > > +       tny-header-test.c \
> > > +       tny-folder-store-query-test.c \
> > > +       tny-account-store-test.c \
> > > +       tny-platform-factory-test.c \
> > > +       tny-test-object.c
> >
> >
> > --
> > Philip Van Hoof, software developer
> > home: me at pvanhoof dot be
> > gnome: pvanhoof at gnome dot org
> > http://www.pvanhoof.be/blog
> >
> >
> >
> >
> >
--
Philip Van Hoof, software developer
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
http://www.pvanhoof.be/blog








[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]