LI18NUX 2000 Specification

Automatic Test Scenarios

Update 22 Apr 2002

Note (25 Sep, 2002):
This page and the above linked pages were used for the Li18nux2000 Level.1 Certification *Pilot* Program.
(The LI18NUX2000 Certification Pilot program refers to LI18NUX2000 amendment 2.)
These pages are not maintained now.

Here is a guide to the installation and execution for the Li18nux2000 test suite.
Following three files are required for the Li18nux2000 test suite execution.

tet_vsxgen_1.0.tgz
contains TET and the VSXgen framework. It is needed to run the test suites.
lts_li18nux_L1_YYYYMMDD.tgz
Li18nux2000 test suite
install.sh
Installer/Setup script

Note:
This testsuite cannot find the aliases of a shell.
So the testsuite return failure against utilities which are aliases of other commands. (e.g. When `vi' is defined as an alias of vim command, the i18n functionality of `vi' is fine, but testsuite returns failure.)

Installation Instructions

Download the above three files
- tet_vsxgen_1.0.tgz <-- (TET/VSXgen framework)
- lts_li18nux_YYYYMMDD.tgz <-- (Li18nux2000 test suite)
- install.sh <-- (Installer/Setup script)
Ensure that all of the files downloaded are in the same directory and execute the install.sh script as root. The script will look after the creation of the test user accounts (vsx0, vsx1 and vsx2) and groups (vsxg*, supp*).
Here is an example of the execution of install.sh.
Logout from the system after you finish all your application programs and X Window

Execution Instructions

Login as vsx0 user
Start X Window system
Run `../setup.sh' script file
Here is an example of the execution.

In order to rerun the test suite at a later date, run the
`$HOME/rerun_tests'
program as the vsx0 user below.
```
$ rerun_tests
```

Test results

The `setup.sh` and `rerun_tests` shell script files generate the result report of test execution to the `$HOME/results/report' file.
*) If you want to get a report as HTML file, refer to Note 2.

Each word of the result means the following:

Succeeded	Implementation satisfies the assertion.
Failed	Implementation does not satisfy the assertion.
Further Information	Implementation does not satisfy the assertion, but the situation described in the assertion is not occurred in reality.
Unsupported	The specification does not require the implementation always satisfies the assertion. But a document which explains how to satisfy the assertion is required when the implementation does not satisfy assertion.
Untested	The situation described in the assertion is not occurred. So the test program does not exist.
Unresolved	The test program of the assertion is terminated abnormally.
Unreported	The test program of the assertion is terminated, and the reason why it is terminated is ambiguous.

You need to do some actions the following results to conform the LI18NUX2000 globalization specification.

Failed, Unresolved, Unreported
You have to remove the problem.
Unsupported
You have to prepare a document which explains how to satisfy the assertion.

But the assertion is included in the waiver list, you don't have to do actions for it immediately.

NOTES:

The script files for the installation and execution are interactively executed. In this case, the inside of a bracket indicates the default value.
The results of all the tests are collected into one journal file under the `results/NNNNe/' directory in an uniform way, where `NNNN' indicates a sequential number from 1, and `e' indicates that it is a result in the test execution.

To generate report file from a journal file directly, you can use the `vrpt' command below.
```
$ vrpt results/0002e/journal
```
To generate report HTML file from a journal file directly, you can use the `jnl2html' command below.
(jnl2html: Source, x86 binary)
```
$ jnl2html results/0002e/journal
```
If you have a file which conatins the list of waivers, you can get the report which includes the information of waivers with jnl2html command.
The waiver list file is here.
```
$ jnl2html results/0002e/journal waiverlist.txt
```
If you want to execute test per testset/area, you can use `build' command with a testset/area name argument below. In the execution without an arguments, the area/testset names list will be displayed.
```
$ build env
```
```
$ build gui
```
The Li18nux2000 test suite contains SRC/subset and tset directories which contains test set code. It also should contain a scripts/li18nux2000-level1 directory which contains scripts which are to be run at suitable times during the setup and installation of the installed test suites.