Handle security test failures
authorPawel Winogrodzki <pawelwi@microsoft.com>
Fri, 24 Feb 2017 01:28:17 +0000 (17:28 -0800)
committerKevin Kane <kkane@microsoft.com>
Mon, 6 Mar 2017 20:37:50 +0000 (20:37 +0000)
commit9339085259310d13fae2cb2c0a40ed366c1004b8
treed9363acafa791ca694b7138cacc0a93e12081602
parent46467a7dd8bae4c3b17519eeee01f2fc80fe3a6b
Handle security test failures

Disable SRPSaveTrustCertChain* which always fail (IOT-1846)
Fix typo in "TLSAdaper"
Disable TLSAdapter tests that have socket bugs (IOT-1848)
Change exit() calls to EXPECT calls so tests continue gracefully
Make socketOpen_server() work on Windows

Change-Id: Ie2b027a4539845975667709ef60497c345fae2b0
Signed-off-by: Pawel Winogrodzki <pawelwi@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/17489
Reviewed-by: Dave Thaler <dthaler@microsoft.com>
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Oleksii Beketov <ol.beketov@samsung.com>
Reviewed-by: Kevin Kane <kkane@microsoft.com>
resource/csdk/connectivity/test/ssladapter_test.cpp
resource/csdk/security/provisioning/unittest/secureresourceprovider.cpp