UNIX V7 Testing Checklist
You are here: Testing > Branding > Product Registration Checklists > UNIX V7
A checklist of what is needed to register a UNIX V7 product
This checklist comprises the following parts:
UNIX V7 Summary of Registration Requirements
A Trademark License Agreement needs to be in place or must accompany the application together with a letter detailing the royalty agreement with The Open Group.
Please complete a test campaign definition form to The Open Group prior to commencing your test campaign.
Product Standard registration application forms need to be completed and signed. A covering letter bringing together the contents of the application and any other relevant information such as purchase order number (if the purchase order is not enclosed) is also requested.
The UNIX V7 Product Standard is made up of the following constituent Product Standards:-
It optionally can include the following Product Standard:
The constituent Product Standards need to be either registered in advance or all registered at the same time as the main Product Standard. They need to be presented with their individual Conformance Statements and indicator of compliance where necessary, please see details below.
In order to keep the amount of paper and processing time to a minimum we are only asking for the legal forms and those pages from the test reports which need signing and/or dating in hard copy.
A summary of what we need is:- (any essential extra detail is provided below under specific Product Standards)
Further detailed notes on the above set out by Component:-
For each test suite a journal is required from an uninterrupted test run using the test suite supplied or test suite generated scenario files.
For test results, please refer to general requirements for uploading electronic files above, only extra specific files/outputs are inserted below under the particular Product Standard.
Internationalised System Calls & Libraries Extended V4
C Language V2
ISO-C the requested output files from a valid release of either the Perennial or Plum Hall test suites.
The test suite is CVSA.. Submit the test results per the 'Perennial CVSA C99
Conformance Validation Procedures'. You can obtain the CVSA procedures by logging in
to the Customer Login area on the website (www.peren.com), and selecting
"CVSA". The procedures are also contained in the /doc directory in the
Plum Hall: The test suite is CVS, the following is needed:
1. A copy of the controlling script used to harness the suite (could be
a makefile or shell script, batchfile etc.), and the copy of envsuite used
to 'source' the suite's environment.
For Perennial & Plum Hall please submit the results by ftp or email the files to the Conformance Administrator. For UNIX V7 conformance the ISO C compiler is required to be the c99 utility.
Commands & Utilities V5
A completed Conformance Statement Questionnaire for Commands and Utilities Version 5.
Test results from VSC5 in a single run in UNIX 10 mode.
For VSC5, the bldfillst tool has been removed. Its use is no longer required when submitting VSC test results for certification.
A uuencoded copy of the "vrpt -L54 JournalFile" output. and "vrpt -L54 -lsect JournalFile"
A uuencoded tar archive containing all files in the ImplSpec directory.
Internationalised Terminal Interfaces V2
A completed Conformance Statement Questionnaire for Internationalised Terminal Interfaces V2.
There are two options, for 'hard' conformance the indicator of compliance is VSU5. For 'soft' conformance there is no indicator of compliance and the CSQ should be completed accordingly.
Conformance Statement Questionnaires
Conformance Statements should be completed and emailed back to The Open Group.
UNIX V7 Brand Requirements versus Test Suites
© The Open Group 1995-2018