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
Unify redis interaction in a class
* allow passing partial config via new()
config will be merged using defined defaults so
missing keys will be appended using values from defaults
Change-Id: I486637e99e0e36fbe1f5a06c703c6b7d2fa77d77
The new function behaves like NGCPDlgCounters:is_in_set but
it uses a regex match to see if the key is contained in the list
Additionally added the helper function 'contains_regex' in the
utils.lua
* ignore vscode files
Change-Id: Iee89f5298ced10c2a9cdf7ebc19a4c0945b8cc9d
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
We are going to use both modules app_lua and app_lua_sr until we
solve the missing pieces on KEMI:
* KSR.pvx.xavp_get() returns a string like '<<xavp:%p>>' not a table like
sr.xavp.get()
* KEMI lacks of something like sr.xavp.get_keys() funtion
So, migrate everything that we can to KEMI and keep using sr approach
for just that two cases
- mocks/sr.lua: use same objects for same behaviour
Change-Id: I475ff8f820586cdc94c75bff7466238215e05673
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
The count argument influences the operation in the following ways:
* count > 0: Remove elements equal to value moving from head to tail.
* count < 0: Remove elements equal to value moving from tail to head.
* count = 0: Remove all elements equal to value.
Change-Id: Ia77b760fcada0027fe58a48f4b335d5c264e8917
Victor Seva
Marco Capetta
Andrew Pogrebennyk