We show how to change the expected “anonymous” caller id string in the config file, instead of by modifying the call script.
|
A tricky aspect of having call testing work on different switches: different delays and timeouts are required throughout the script library. When a telephony call feature is failing, there are several possible categories of causes. The early stages of troubleshooting should try to eliminate some of these broad categories as causes (or find the cause along the way, whichever happens first). Speed dial 8 is a call feature that allows a subscriber to dial a number using a reduced number of dialed digits. Speed dial is generally a digit between 2 and 9 followed by “#” (pound or hash). Speed dial 8 numbers are usually set by dialing *74 and following the prompts. Let’s outline what the test scripts for speed dial 8 would look like. The bad news is that the bugs that are left are hard to find. Forcing external failures during call generator testing will help flush them out. Looking for ideas to find bugs? Configure your call generator to run your entire test suite with DTMF tones near the minimum width. Sometimes a feature is broken in a way that is not immediately detectable by the call generator. For instance, let’s say some call flow causes a memory leak in the switch. The call will work hundreds or thousands of times, but at some point the entire switch will stop working — and the cause won’t be obvious. You want your switch to crash and burn in your lab, not in the field. Let’s look at three types of robustness testing. If you can reproduce the bug by hand, you can script the call generator to force it. Even if it is hard to reproduce reliably, it may be easy to force it every time with the help of automation. There are a huge number of possible test cases for even a relatively simple telephony feature when multiple interop combinations are involved. How do we manage all of this? The distinction between chaining and stacking is maybe too subtle but I think of them differently when planning tests. “Chaining” is what I call it when a test repeatedly invokes a single feature in a single call flow. |
|
|
Copyright © 2010 Rimay Technologies, LLC - All Rights Reserved - Follow us |
|
