Fix RE unit test case. (#632) 03/218803/1 accepted/tizen/unified/20191201.221455 submit/tizen/20191128.075235
authorsenthil.gs@samsung.com <senthil.gs@samsung.com>
Thu, 28 Nov 2019 06:34:25 +0000 (12:04 +0530)
committerDoHyun Pyun <dh79.pyun@samsung.com>
Thu, 28 Nov 2019 07:28:51 +0000 (16:28 +0900)
commit51d4d12cacb66851fb3f52b5d8af5bf507669f30
treec74eb45b202efd3a9935770a40e3bc2629206294
parent70fe9239d3c115e636410da4629f5105f72d2f41
Fix RE unit test case. (#632)

Unit test case which was failing:
RemoteResourceObjectTest.IsCachingReturnsTrueAfterStartCaching()

Reason for failure: Shared pointer reference for RCSRemoteResourceObject
was not released. Due to which, there was a problem in tearing down the test case.

This PR has the fix.
Additionally, application will receive caching callback
from RCSRemoteResourceObject only if remote resource object is available.

https://github.sec.samsung.net/RS7-IOTIVITY/IoTivity/pull/632
(cherry-picked from e8fb156d8239ace91f9529830f4781ea16e85bd3)

Change-Id: Idf587d1f5add4360a717a6959dcc839bc7aacb9f
Signed-off-by: Senthil Kumar G S <senthil.gs@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
service/resource-encapsulation/include/RCSRemoteResourceObject.h
service/resource-encapsulation/src/resourceClient/RCSRemoteResourceObject.cpp