TET (Test Execution Toolkit) from the X/Open Consortium is a multi-platform
test scaffold for both distributed and non-distributed test suites.
TET allows the production of test suites sharing a common interface,
promoting sharing of test suites within and across organizations.
It allows facilities to execute test cases in several ways:
- Execution of non-distributed test cases on the local system.
- Execution of non-distributed test cases on one or more remote
systems.
- Execution of distributed test cases with the parts of each test
case executing simultaneously on either the local system and one
or more remote systems, or entirely on two or more remote systems.
- Execution of a single test case selected at random from a list of
test cases.
- Combinations of the above elements executing in parallel.
- Sequences of the above elements executing a specified number of
times or until some time period has expired.
WWW: http://tetworks.opengroup.org/documents/docs37.htm
===> The following configuration options are available for tet-3.7:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
According to the Porter's Handbook (5.12.2.3.) default options must be added to
OPTIONS_DEFINE. This policy has been implemented only recently that's why we
have many ports violating this policy.
This patch adds the default options specified in the Porter's Handbook to
OPTIONS_DEFINE where they are being used. Ports maintained by
gnome@FreeBSD.org, kde@FreeBSD.org and x11@FreeBSD.org have been excluded.
Approved by: portmgr (bapt)
- Set IGNORE if TET_ROOT not defined instead of hitting an error
while building packages. Did not use MANUAL_PACKAGE_BUILD as
maybe someone is building packages and has TET_ROOT defined for
the port.
With hat: portmgr
Cleanup unmaintained ports in the misc category:
- Trim Header
- Convert to OptionsNG
- Prefer DISTNAME to DISTFILES
- Reorder variables
- Fix comments (don't include leading article)
- @unexec rm must not cause failure
- Tabs, not spaces
- Single space for WWW
- Pet portlint
- etc.
In a few cases the option DOCS was used to control installation into EXAMPLEDIR.
I opted to keep the existing logic of the port in these cases.
Reviewed by: koobs, ashish
- Upgrade to v3.7.
New upstream features include:
+ Distributed TETware has a 'Transfer Source Files' phase.
+ More flexibility in handling real-time signals in the C API.
+ APIs for Java, Python, Ruby, Perl, Tcl, PHP. These have
not been turned on in this version of the port.
- Install PDF documentation under ${TET_ROOT}/doc unless NOPORTDOCS
is specified.
Unbreak port by merging the build and install phases. Create a PLIST
dynamically so that pkg_delete works. Make the Makefile and pkg-descr
portlint clean.
