When a test finishes we currently check if there are active calls/registrations/subscriptions and terminate them.
This was done as a convenience for the developer as the next test would not be affected by an unexpected state in the remote sip server under test.
However this causes some issues:
it make the test scripts to take longer to finish
we actually eventually might want to see the current state of the remote sip server and doing this shutdown would change it
So we will disable this.
Then the writing of test scripts using sip-lab would be:
if a test fails, the state of the remote sip servers will be preserved
it is the responsibility of the test script to clear the remote sip servers state before starting the test
This way, debugging/troubleshooting will be eased.
Then, if in the future this becomes somehow necessary, we can add a flag to be used upon sip-lab initialization to permit to enable/disable it.
When a test finishes we currently check if there are active calls/registrations/subscriptions and terminate them. This was done as a convenience for the developer as the next test would not be affected by an unexpected state in the remote sip server under test. However this causes some issues:
So we will disable this. Then the writing of test scripts using sip-lab would be:
This way, debugging/troubleshooting will be eased.
Then, if in the future this becomes somehow necessary, we can add a flag to be used upon sip-lab initialization to permit to enable/disable it.