| Summary: | ASTERISK-24091: Testsuite - SIPpTestCase modules report success on reactor timeout. | ||
| Reporter: | Jonathan Rose (jrose) | Labels: | |
| Date Opened: | 2014-07-22 12:43:01 | Date Closed: | |
| Priority: | Major | Regression? | No |
| Status: | Open/New | Components: | Tests/testsuite |
| Versions: | Frequency of Occurrence | Constant | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Suppose we have a SIPpTestCase as the only module of a test. The SIPp scenario that it runs sends Asterisk a message of some sort and then waits for a response, but the response never arrives and the scenario waits until Reactor times out.
At this point, we expect the test to fail since the scenario didn't complete successfully. However, at reactor timeout SIPp scenarios are manually shut down, and when they do, they trigger the processEnded function in SIPpProtocol. SIPp's exit code is the same for early termination as it is for successful completion, so we can't really distinguish whether the test was successful or if it was terminated by the reactor timeout based on exitcode alone. At the moment, we are trying to do so and this means that reactor timeouts are tripping this function and setting the test to passed. | ||
| Comments: | |||