-
Notifications
You must be signed in to change notification settings - Fork 2.1k
/
Copy pathAppTestContext.cpp
90 lines (74 loc) · 3.2 KB
/
AppTestContext.cpp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
/*
* Copyright (c) 2021 Project CHIP Authors
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#include "AppTestContext.h"
#include <access/AccessControl.h>
#include <access/examples/PermissiveAccessControlDelegate.h>
#include <app/InteractionModelEngine.h>
#include <app/reporting/tests/MockReportScheduler.h>
#include <lib/core/ErrorStr.h>
#include <lib/support/CodeUtils.h>
namespace {
class TestDeviceTypeResolver : public chip::Access::AccessControl::DeviceTypeResolver
{
public:
bool IsDeviceTypeOnEndpoint(chip::DeviceTypeId deviceType, chip::EndpointId endpoint) override { return false; }
} gDeviceTypeResolver;
chip::Access::AccessControl gPermissiveAccessControl;
} // namespace
namespace chip {
namespace Test {
void AppContext::SetUpTestSuite()
{
LoopbackMessagingContext::SetUpTestSuite();
VerifyOrReturn(!HasFailure()); // Stop if parent had a failure.
ASSERT_EQ(chip::DeviceLayer::PlatformMgr().InitChipStack(), CHIP_NO_ERROR);
}
void AppContext::TearDownTestSuite()
{
// Some test suites finish with unprocessed work left in the platform manager event queue.
// This can particularly be a problem when this unprocessed work involves reporting engine runs,
// since those can take a while and cause later tests to not reach their queued work before
// their timeouts hit. This is only an issue in setups where all unit tests are compiled into
// a single file (e.g. nRF CI (Zephyr native_posix)).
//
// Work around this issue by doing a DrainAndServiceIO() here to attempt to flush out any queued-up work.
//
// TODO: Solve the underlying issue where test suites leave unprocessed work. Or is this actually
// the right solution?
LoopbackMessagingContext::DrainAndServiceIO();
chip::DeviceLayer::PlatformMgr().Shutdown();
LoopbackMessagingContext::TearDownTestSuite();
}
void AppContext::SetUp()
{
LoopbackMessagingContext::SetUp();
VerifyOrReturn(!HasFailure()); // Stop if parent had a failure.
ASSERT_EQ(app::InteractionModelEngine::GetInstance()->Init(&GetExchangeManager(), &GetFabricTable(),
app::reporting::GetDefaultReportScheduler()),
CHIP_NO_ERROR);
Access::SetAccessControl(gPermissiveAccessControl);
ASSERT_EQ(Access::GetAccessControl().Init(chip::Access::Examples::GetPermissiveAccessControlDelegate(), gDeviceTypeResolver),
CHIP_NO_ERROR);
}
void AppContext::TearDown()
{
Access::GetAccessControl().Finish();
Access::ResetAccessControlToDefault();
chip::app::InteractionModelEngine::GetInstance()->Shutdown();
LoopbackMessagingContext::TearDown();
}
} // namespace Test
} // namespace chip