OpenI18N 1.3 Specification

Automatic Test Scenarios

Update 16-Nov-2002

Here is a guide to the installation and execution for the OpenI18N 1.3 Level.1 conformance test suites.
Following three files are required for the OpenI18N 1.3 Level.1 conformance test suites execution.

The current test suites status is the following:

Note:

Installation Instructions

  1. Download the above three files.
     - tet_vsxgen_openi18n_2.9.tgz <-- (TET/VSXgen framework)
     - lts_openi18n_lv1_1.3.0-1.tgz <-- (OpenI18N 1.3 Lv.1 conformance test suites)
     - install.sh <-- (Installer/Setup script)

  2. Ensure that all of the files downloaded are in the same directory.

  3. Ensure that C, C++ Compiler and yacc(byacc) are installed.

  4. Execute the install.sh script as root user.
    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.

Execution Instructions

  1. Login as vsx0 user.

  2. Start X Window System.

  3. 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' script file.

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 4.

Each word of the result means the following:

Succeeded Implementation satisfies the assertion.
Failed Implementation does not satisfy the assertion.
Warning Implementation does not satisfy the assertion. But the assertion is waived currently.
Further Information Provided Some Informations, such as the result of interactive test, are necessary for determination of the results.
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 OpenI18N 1.3 globalization specification.

Web Certification

The journal file of this test suites is required at the web certification. (And each result of interactive tests is required.) When you make a journal file to submit to the web certification system, please follow the following description to produce the exact result.

  1. If some test suites ran on the target system using TET/VSX test framework (for example, OpenI18N or LSB test suites ran on your system before), delete the installed files. The following is the example of how to do that. 
    $ su
# rm -rf /home/tet
  2. Install the test suites according to the Installation Instructions.
  3. Execute the test suites according to the Execution Instructions.

The journal file which is required by web certification system is made in the `~/results/0002e/' directory.

When the journal file has some FIP code, you have to prepare a document which explains how to satisfy the assertion.

The following test results may be FIP (Further Information Provided).

Section target No. Assertion
Annex locale 2 Check that some locales listed in Annex B (except the locale which marked with [Support of this locale is level2]) are provided and the others are documented how to install it.
Annex locale 3 Check that the above locales are supporting UTF-8 as a codeset at least.
gui language_support 1 Verify that the languages (except CTL languages) listed by Annex B are supported by setlocale() and XSupportsLocale() functions.

The following test results are always. You have to do the manual test.

Section target No. Assertion
utils vi 1 Verify that the cursor can move per 1 character.
utils vi 2 Verify that this utility can delete per 1 character.
utils mailx 1 Verify this utility handles case-insensitive address correctly. (i.e. both the address `foo' and `FOO' are handled in the same way.)
utils general_text_editor 1 Verify cursor can move per 1 character in the text encoded in UTF-8
utils general_text_editor 2 Verify this utility can delete per character in the text encoded in UTF-8.
utils terminal_emulator 1 Verify if locale dependent charset can be displayed.
utils terminal_emulator 2 Verify if cursor can be displayed on double width character correctly.
utils terminal_emulator 3 Verify if double width character is wrapped on the edge of terminal window.
im imtest 1 Verify that X Input Method Servers, which support UTF-8 encoding and allow user to input whole repertoire of Unicode 3.0, are supported.
om omtest 1 Verify if locale dependent charset can be displayed.
internet web_browser 1 Verify that Web browsers, for example Mozilla, are able to input and output all the characters of the each locale described by Annex B.
internet mua 1 Verify that mail user agents, for example Mozilla, are able to input and output all the characters of the each locale described by Annex B.


NOTES:

  1. The script files for the installation and execution are interactively executed. In this case, the inside of a bracket indicates the default value.

  2. This testsuite cannot find the shell aliases.
    So the testsuite returns 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.)

  3. All test program included in this test suites run on a special locale `LTP_1.UTF-8'.
    If you want to cut one test program from the testsuite and make the test program run, unset all locale environment variables and substitute LTP_1.UTF-8 for LANG variable.

    The following is the example of how to do that. 
    $ for i in `locale | cut -f 1 -d '='` ; do unset ${i} ; done
$ LANG=LTP_1.UTF-8 ; export LANG
  4. 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
  5. Please note that for the official certification any issues will need to be resolved through a official problem report at the certification web site.