We were using a mix of .new() and :new() and
that lead us to errors when calling new with parameters
Just be consistent and choose one
Change-Id: Icc2078efb377b80942b2fb518db52df339ecda6a
https://www.lua.org/manual/5.2/manual.html#8.3
> (Modules are not expected to set global variables anymore.)
EXPORT_ASSERT_TO_GLOBALS was just there for backwards compatibility
Change-Id: I11ac6d24746ca3c965b16ad523efff1f12ef0e9a
In the new version of LuaUnit assertTrue() and assertFalse()
functions are changed to striclty evaluate that the data is
True or false.
Where necessary the fuctions have been substituted in the test
with the new assertEvalToTrue() or assertNil().
Change-Id: I0c728323752a4458e93f516c7529670433c516d1
* fix pv mock to align kamailio behavior with pv_unset() for avps.
It removes only the first value not all, only when using '[*]'
pv_unset("$avp(name)") != pv_unset("$(avp(name)[*])")
pv_unset("$avp(name)") == pv_unset("$(avp(name)[0])")
pv_unset("$(avp(name)[1])") == pv_unset("$(avp(name)[0])")
Change-Id: I1aab2150d288da546b144388adb7b2f87ecfb069
Victor Seva
Marco Capetta