tests: unittest: Add new test for hal_common_get_backend_with_library_name 00/276600/3 accepted/tizen_7.0_unified_hotfix tizen_7.0_hotfix accepted/tizen/7.0/unified/20221110.060157 accepted/tizen/7.0/unified/hotfix/20221116.110326 accepted/tizen/unified/20220715.141321 submit/tizen/20220714.022505 submit/tizen/20220715.020027 tizen_7.0_m2_release
authorChanwoo Choi <cw00.choi@samsung.com>
Tue, 21 Jun 2022 15:58:01 +0000 (00:58 +0900)
committerChanwoo Choi <cw00.choi@samsung.com>
Wed, 22 Jun 2022 03:15:02 +0000 (12:15 +0900)
commit8eb86b233dff2c718bda0cbc20a3a2a8fa3dae61
tree7ee8ad3882e82d1c0028f4215465b9e59c699c6f
parent471e3222a40b1ac50d495f45e872049cb3eef52a
tests: unittest: Add new test for hal_common_get_backend_with_library_name

Basically, the hal backend library name of each module is already decied
such as 'libhal-backend-[module name].so'. But, some module requires
the hal backend library loading way with their own library name
like 'libhal-backend-[module name]-lidar.so'.

When loading the their own library name, hal_common_get_backend_with_library_name
and hal_common_put_backend_with_library_name are used.

So that add new for hal_common_get/put_backend_with_library_name
and add 'backend_module_name' attribute to class HalInfo
because 'backend_module_name' is required to check the hal backend name
as I mentioned above.

Change-Id: Idbd5ae4f23714a4efdb857d2a1ed0885a927e887
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
tests/unittest/test-hal-api-common.cc