Testing and Telephony
• Tuesday, July 13, 2010 - It does WHAT? My SUT can still surprise me
| I configured my SUT for SIP, and made sure that it still registers correctly with my lab SIP proxy - it's one of those things that I don't test all that often because that area of code just doesn't get messed with, and having it on or off really doesn't affect my test scenarios, but I do test it occasionally because some customers do use it. And then I also turned on a mode in the product that we support, but no customers use, because after all, some day some customer might want it, and after we went to all that trouble to implement it, it is worth the occasional brief test just to make sure nothing has died horribly. And I discovered ... that combination causes some additional resources to be registered. I was not expecting the SUT to do that, but OK, that actually is proper behavior, only the registrations are not expiring correctly, and not all of those additional resources that should be, are actually being registered. So I went looking into the source code, and discovered that the implementation (which happened before I came to work here) had not been finished - there were nice prominent TO DO labels on comments near the relevant code, discussing the missing functionality. No one has ever cared about this, for several years now ... well, some day someone might care, so I put in a bug for it, explaining what I'd found. I'm pretty sure I'll get some warning if we ever do get a customer wanting to use this mode, and a good thing too, because it really ought to have some extra testing before it gets used for real. |
:: Send to a Friend!
|
|
|
|
|
