You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

NSS 3.1 Test Suite

NSS 3.1 Release, 17 October, 2000

Newsgroup: mozilla.dev.tech.crypto
Engineering lead: Bob Relyea
Product manager: Roland Jones
Engineering manager: Wan-Teh Chang

Running the Test Suite

Before running the NSS test suite, you should first build NSS and successfully perform the initial tests as described in Build Instructions for NSS 3.1. You must also have the MKS toolkit installed.

Make sure the variable DOMSUF is set to the domain suffix, without an initial dot; for example, mydomain.com. On Solaris, if you are not sure, type:

    cat /etc/defaultdomain
to obtain the domain name, then
    setenv DOMSUF domainname
Alternatively, you can combine these steps as follows:
    setenv DOMSUF `cat /etc/defaultdomain`

HOST must be defined and must contain only the host name, without the domain suffix:

    On NT: Set HOST and HOSTNAME manually to the name of the PC (usually defined the environment variable COMPUTERNAME).

    On Unix: HOST is usually defined. Some Unix flavors (such as Linux) define HOST to be a fully qualified name (with the domain suffix), in which case you need to set HOST to just the host name.

The test script constructs the fully qualified name as ${HOST}.${DOMSUF}.

To test the optimized build set BUILDOPT to 1:

    setenv BUILDOPT 1

To start all.sh from a nonstandard location you also need to set DIST.

To execute the tests on the build directory, execute these commands:

    cd builddirectory/mozilla/security/nss/tests
    all.sh

The output will be written to builddirectory/mozilla/tests_results/security/machinename, QAnumber. The most interesting output files are results.html and output.log.

Note: The SSL stress test opens 2,048 TCP connections in quick succession. Kernel data structures may remain allocated for these connections for up to two minutes. Some systems may not be configured to allow this many simulatenous connections by default; if the stress tests fail, try increasing the number of simultaneous sockets supported.

Known Problems With the NSS Test Suite

  • DOMSUF should be set automatically.
  • The return codes need fine tuning. Currently, only pass/fail is possible.
  • Failures come back differently on UNIX and NT.
  • SDR always fails.