Added AwaStaticClient_ResourceChanged

[ghost]

One working test for AwaStaticClient_ResourceChanged is in
place but it needs to be cleaned up and parameterised.

Added a temporary mapping between Lwm2mResult and AwaLwm2mError
although these enums should really be combined.

Renamed some wrongly spelt variables in test_client.cc

Signed-off-by: Roland Bewick [email protected]

[ghost]

Needs assertions and hardcoded values removed

[DavidAntliff]

The tests for this feature don't need threads - try this:

1. create observation on server
2. perform observation on server
3. change value on static client - call ResourceChanged()
4. use a subclassed WaitCondition to continually call static client process, and be calling server process within the wait loop. Loop terminates when server callback fires and sets a loop exit flag.

This would be preferable to multiple threads, which can be difficult to maintain and understand.

[cdewbery]

@david-antliff-imgtec You don't need a thread for steps 3 and 4, but I think you still need a thread to create the initial observation, as the AwaServerObserveOperation_Perform() function is a blocking operation and won't complete until it times out (resulting in a error) or succeeds which requires AwaStaticClient_Process() to be called called.

for example:

• Server thread - AwaServerObserveOperation_Perform() - sends observe to client, then blocks waiting for response.
• Client (aka test code) - AwaStaticClient_Process(), handles observe request, sends response to server.
• Server thread - AwaServerObserveOperation_Perform() completes.

[DavidAntliff]

@chris-dewbery-imgtec yep, fair comment, we missed that.