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

current status of test suites



I'm forwarding a note from Andrew Josey relating the current state of
the LSB test suite located on sourceforge.net.

The only people actively working on the test suites right now are
Andrew and Dale Scheetz, but it's now at the point where more people
can start getting involved, running the test suite, adding to it, etc.

 - Dan

------- start of cut text --------------
From: Andrew Josey <ajosey@rdg.opengroup.org>
To: quinlan@transmeta.com
Subject: Re: LSB conference call - February 16th
Date: Wed, 16 Feb 2000 07:26:42 GMT

hi Dan
The current status is as follows:

The basic framework layers have been imported
into sourceforge

These are the

TET (test environment toolkit) framework layer
VSXgen - a generic framework part of the VSX test suite
   into which you can plug testsets into
VSX-PCTS testset has been imported (for POSIX.1)
the LSB-FHS testset has been imported (for FHS)

We're just updating the TET version to the latest, and need
to make a fix to it, for some changes in the g++ compiler
that blow up on one prototype

The LSB-FHS testset needs to be updated for the final FHS 2.1

Looking at the output of the SQL database it seems we should
be able to get some binary level tests for the c compilation
system automatically generated

We need to do some coverage analysis of what remains, and identify
lumps of test coverage that could be split out into work items.


Later on, we'll need to consider whether the final test suites for
certification
will be binary versions of  these suites, built on the reference
implementation, or whether we builds from source are allowed,
we would always supply the source for reference, but there are some
merits for having an ABI test suite supplied as  a binary. For
example the C compilation system tests can be built using a reference
set of headers built from the SQL database, and hence known to
be clean.

Hope that helps
regards
Andrew
------- end ----------------------------


Reply to: