wiki:release-testing

Testing

Memory Leak Testing

  • Use drop bts connection <0-65535> (oml|rsl) to drop the OML and RSL connection from software, maybe use a simple script that sends these commands via telnet and has a big sleep loop to drop the connection every couple of minutes
  • Use tcpkill of dsniff to kill the TCP connection of the OML, RSL, CTRL, ... connection like we do above. This way we get connection drops at different points
  • Use the talloc reporting to see if some buffer is growing, normally also means to see which regions are missing

Call Testing

  • Use AT commands to repeatingly dial, preferable with forcing RF failures at that time... but it is difficult to test every error path. There is a script in the contrib directory.

Last modified 3 years ago Last modified on Sep 15, 2011, 2:33:37 PM