RELEASE 2 TEST PLAN
===================

Created by David Rowe 8/8/03
Updated by Ben Kramer 16/8/03

1. Introduction
---------------

This document describes the tests and results used to test the Release
2 OpenPBX software.  It is a "soft" document, designed to be maintained
using CVS so that multiple people can modify it at the same time.
Adding extra tests at any time is encouraged, for example if you think
a particular section can be better tested feel free to add and
perform the test.

Section 2 describes when and how to perform regression testing.
Regression testing is highly recommended if you make ANY code mods,
for example a minor mod after the formal release or Release 2 code.

2. When to Perform Regression Testing
-------------------------------------

- If u perform ANY MODS to the PBX code, AS A MINIMUM you MUST run
  thru and PASS:

  a) All of the functional tests (Section 3).
  b) Overnight performance test(s) (Section 4).

- A good configuration for Section 3 type of testing is test000.conf
  in the perlpbx/tests dir.  Also see test000.sh for set up
  instructions.

- When using a OpenSwitch12 board for running single machine tests all 
  that is needed is one regular ethernet cable. This needs to be plugged
  between the top and bottom ports on the OpenSwitch12. You should have 
  the jumper settings as per "factory", ie 4 trunk ports and 8 station
  ports.  You don't need to connect any phones or trunks, the test code
  simulates these.

- When using two machines and two OpenSwitch12 boards, you will need to
  set up the call generator board as 8 trunks and 4 stations. You then
  connect 3 ethernet cables between each port, ie top port to top port,
  middle port to middle port and bottom port to bottom port.

3. Functional Test Plan
-----------------------

Work through the sections, adding the date the test passed and your 
initials and comments on the tests if required.
If a section has a dependency, you must confirm that the dependency also
passes before the section can be passed.

4. Performance testing
----------------------

These are fully automated tests, that running the pbx scripts on a few
ports and test scripts on other ports to simulated handsets and trunks 
lines. The shell scripts that start these tests describe their pass/fail
conditions for each iteration. Each script must run for 1000 iterations
to PASS.

5. Conclusion
-------------

Once all the tests for each Milestone have been passed, the product can 
be considered ready for full release.
