Summary:ASTERISK-20020: Write call parking test plan
Reporter:Matt Jordan (mjordan)Labels:
Date Opened:2012-06-18 13:48:02Date Closed:2012-06-26 16:04:28
Versions:Frequency of
Description:In, a (slightly) innocuous code change broke call parking.  Luckily, it was caught in a release candidate, and thus no parking lots were destroyed in the making of that release.

On the other hand, this calls to attention the current state of our call parking tests.

- blind-transfer-parkingtimeout: currently skipped.  This should have caught this regression, but wasn't run.
- callparking_retrieval: currently skipped; written in bash.  Some subset of the functionality covered by this test may be covered by callparking.

- one-step-parking - tests feature one step parking only

- callparking - a test that covers one-step, blind transfer, and attended transfer using findslot=next.

There are a number of features that are not covered by these tests.  A test plan ideally would have:

* What features we would like tests for and how they should be tested
* What features we have tests for and how they are tested
* What features we will not write tests for, i.e., adsipark

In addition, the 'skipped' tests should either be removed from the test suite if their functionality is covered by other tests, or they should be refactored, fixed, and re-enabled.