Bsc nat release » History » Version 3
Anonymous, 02/19/2016 10:48 PM
| 1 | 1 | ||
|---|---|---|---|
| 2 | 3 | h2. Test Plan |
|
| 3 | 1 | ||
| 4 | |||
| 5 | |||
| 6 | 3 | h3. New Features |
|
| 7 | |||
| 8 | * Test all paths, maybe use gcov to figure out if they are used. |
||
| 9 | * Test success/failure, preferable with a unit test. |
||
| 10 | |||
| 11 | |||
| 12 | h3. Configuration format |
||
| 13 | |||
| 14 | * load with current config |
||
| 15 | * write config via vty |
||
| 16 | * load new config. |
||
| 17 | |||
| 18 | *OBJECTIVE:* Find wrong VTY entries, e.g. wrongly spelled option. |
||
| 19 | |||
| 20 | |||
| 21 | h3. Load Test |
||
| 22 | |||
| 23 | * Attempt to simulate load, e.g. try to force a BSC disconnect while a normal operation is going on. This can be automated with the BSC dropping the MSC connection randomly (via SIGUSR2) while doing call testing or such. |
