OpenServer 5.05 test plan
Squid Proxy Server 2.3.STABLE2 (squid)
Revision: 15.1

Author: Craig Kaes

Revision Date: 1/11/2000


Description

The tests described in this test plan ensure that the OpenServer 5.05 packaging of the Squid Proxy Server 2.3.STABLE2 product is correct. The plan contains tests to ensure that the package can be installed on OpenServer 5.05 using the standard installation tools. It also checks that  the default configuration applied to the package by the packaging is correct.  Where SCO has added extra programs to the final package, these are tested individually.

Objective

The objective of the tests is to ensure that the OpenServer 5.04 packaging of this product meets its marketing requirements.  Tests are designed for maximum coverage of the packaged programs, and of the packaging itself.

Approach

The tests described in this document must be done manually, since no facility has been developed for automated testing of  the Squid Proxy Server 2.3.STABLE2. For all tests, package installation is performed with custom(ADM) and package removal with custom(ADM). Unless otherwise indicated, tests use standard layered installs. Tests should be undertaken on a system with a browser (nsnavAu) installed.

Sanity Tests

Many tests require performing "sanity tests; this section defines what is meant.  After installation, perform the following steps:

Pass or fail
Pass: Squid starts correctly, all requested documents/files download to browser, access log records all requests.
Fail: Squid fails to start, or documents don't load through squid but do load without a proxy server.

Test case: squid.1

Test case name: squid.install.variants

Description: Install the product, remove the product.

Steps:

Pass or fail
Pass: squid installs and passes sanity  tests; on uninstall, squid.conf and swap.state are left behind.
Fail: installation fails, sanity tests fail, swap.state removed, or squid.conf removed.

Test case: squid.2

Test case name: squid.noclobber

Description: Install squid after a previous installation has been removed.

Steps:

Pass or fail
Pass: old squid.conf backed up, swap.state not overwritten, and passes sanity tests.
Fail: old squid.conf not backed up, swap.state overwritten, or fails sanity tests.



Test case: squid.3

Test case name: squid.scripts

Description: Exercise the /etc/squid script.

Steps:
 

Pass or fail

Pass: squid shell script correctly starts, stops, restarts, enables, and disables the Proxy Server as expected; query shows the correct state of the server

Fail: script fails or gives an error message, or does not behave as required


Test case: squid.4

Test case name: squid.remove

Description: Remove the product.

Steps:

Pass or fail

Pass: all elements of the package removed from the system except those explicitly mentioned above.

Fail: any package elements remain besides those explicitly mentioned above.


Test case: squid.5

Test case name: squid.lang

Description: Install squid, verify that error messages are displayed in correct language.

Steps:

Pass or fail

Pass: error message displayed is in Spanish.
Fail: error message not displayed or displayed in any language other than Spanish.


Test case: squid.6

Test case name: squid.lang.exhaustive

Description:  Run testLocale.sh, a shell script that verifies squid installs correctly for all languages.

Steps:

Notes: Pass or fail

Pass:  Message "Locale tests passed." displayed at end of test.
Fail: Message "Locale tests *FAILED*.  See file RESULTS for details." displayed at end of test.