| /openbmc/phosphor-power/phosphor-power-supply/test/ |
| H A D | power_supply_tests.cpp | 39 // Helper function to setup expectations for various STATUS_* commands
41 const PMBusExpectations& expectations) in setPMBusExpectations() argument
45 .WillOnce(Return(expectations.statusWordValue)); in setPMBusExpectations()
47 if (expectations.statusWordValue != 0) in setPMBusExpectations()
54 .WillOnce(Return(expectations.statusInputValue)); in setPMBusExpectations()
57 .WillOnce(Return(expectations.statusMFRValue)); in setPMBusExpectations()
60 .WillOnce(Return(expectations.statusCMLValue)); in setPMBusExpectations()
67 .WillOnce(Return(expectations.statusVOUTValue)); in setPMBusExpectations()
70 .WillOnce(Return(expectations.statusIOUTValue)); in setPMBusExpectations()
73 .WillOnce(Return(expectations.statusFans12Value)); in setPMBusExpectations()
[all …]
|
| /openbmc/docs/ |
| H A D | community-membership.md | 3 This doc outlines the various expectations of contributor roles in OpenBMC. The
7 | Role | Expectations | Requirements …
27 Role-specific expectations, responsibilities, and requirements are enumerated
39 ### Expectations subsection
66 ### Expectations subsection
90 - Expected to be responsive to review requests as per [community expectations]
104 ### Expectations subsection
129 - Expected to be responsive to review requests as per [community expectations]
148 ### Expectations subsection
160 - **Note the following expectations for sponsors**:
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | sensor_monitoring_tests.cpp | 149 // Set I2CInterface expectations in TEST()
155 // Create lambda that sets MockServices expectations. The lambda allows us in TEST()
156 // to set expectations multiple times without duplicate code. in TEST()
177 // Create mock services. Set expectations via lambda. in TEST()
192 // Create mock services. Set expectations via lambda. in TEST()
225 // Set I2CInterface expectations in TEST()
231 // Create mock services. Set Sensors service expectations. in TEST()
267 // Set I2CInterface expectations in TEST()
273 // Create lambda that sets MockServices expectations. The lambda allows in TEST()
274 // us to set expectations multiple times without duplicate code. in TEST()
[all …]
|
| H A D | phase_fault_detection_tests.cpp | 72 * so they can be used in mock expectations.
200 // Create lambda that sets Journal and ErrorLogging expectations when in TEST_F()
202 // set the same expectations twice without duplicate code. in TEST_F()
204 // Set Journal service expectations: in TEST_F()
232 // Set ErrorLogging service expectations: in TEST_F()
247 // Create mock services. Set expectations via lambda. in TEST_F()
263 // Create mock services. Set expectations via lambda. in TEST_F()
287 // Set expectations for regulator I2C interface. Should not be used. in TEST_F()
291 // Set expectations for I/O expander I2C interface. Should be used. in TEST_F()
317 // Set expectations for regulator I2C interface. Should be used. in TEST_F()
[all …]
|
| H A D | system_tests.cpp | 169 // Create lambda that sets MockServices expectations. The lambda allows in TEST()
170 // us to set expectations multiple times without duplicate code. in TEST()
191 // Create mock services. Set expectations via lambda. in TEST()
206 // Create mock services. Set expectations via lambda. in TEST()
269 // Create mock services with the following expectations: in TEST()
448 // Create mock services. Set Sensors service expectations. in TEST()
|
| H A D | chassis_tests.cpp | 215 // Create lambda that sets MockServices expectations. The lambda allows in TEST_F()
216 // us to set expectations multiple times without duplicate code. in TEST_F()
237 // Create mock services. Set expectations via lambda. in TEST_F()
252 // Create mock services. Set expectations via lambda. in TEST_F()
429 // Create mock services with the following expectations: in TEST_F()
569 // Create mock services. Set Sensors service expectations. in TEST_F()
|
| H A D | rail_tests.cpp | 139 // Create lambda that sets MockServices expectations. The lambda allows in TEST()
140 // us to set expectations multiple times without duplicate code. in TEST()
161 // Create mock services. Set expectations via lambda. in TEST()
176 // Create mock services. Set expectations via lambda. in TEST()
373 // Create mock services. Set Sensors service expectations. in TEST()
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 12 populous) group. It provides tips and describes the expectations and
31 The exact expectations on the response time will vary by subsystem.
35 review delay of the subsystem maintainer. The resulting expectations
89 The previous section described the expectations of the maintainer,
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | README.md | 7 through the documented set of the common [requirements and expectations][].
33 [requirements and expectations]: requirements.md
|
| H A D | requirements.md | 1 # Requirements and Expectations for dbus interfaces
3 This document outlines requirements and expectations for dbus interfaces. These
|
| /openbmc/phosphor-led-sysfs/test/ |
| H A D | physical.cpp | 78 /* NiceMock ignores calls to methods with no expectations defined */ in TEST()
88 /* NiceMock ignores calls to methods with no expectations defined */ in TEST()
100 /* NiceMock ignores calls to methods with no expectations defined */ in TEST()
112 /* NiceMock ignores calls to methods with no expectations defined */ in TEST()
124 /* NiceMock ignores calls to methods with no expectations defined */ in TEST()
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | usage.rst | 11 and then sets *expectations* for what should happen. For example:
25 nothing; no expectations are set, and therefore all expectations pass. On the
30 Expectations subsection
34 expectations about the behavior of a piece of code under test. When one or more
35 expectations fail, the test case fails and information about the failure is
51 expectations, the test case, ``add_test_basic`` will pass; if any one of these
52 expectations fails, the test case will fail.
55 continue to run, and try other expectations until the test case ends or is
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
|
| H A D | architecture.rst | 108 KUnit tests verify state using expectations/assertions.
109 All expectations/assertions are formatted as:
116 - For expectations, the test is marked as failed and the failure is logged.
|
| /openbmc/linux/include/kunit/ |
| H A D | try-catch.h | 39 * Assertions are like expectations, except they abort (call
43 * conclusion is a set of predicates, rather expectations, that must all be
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/ |
| H A D | firmware_close_unittest.cpp | 46 /* Set up close() expectations. */ in TEST_F()
76 /* Set up close() expectations. */ in TEST_F()
|
| /openbmc/phosphor-pid-control/test/ |
| H A D | helpers.hpp | 22 /** @brief Setup the expectations for sdbus-based object creation.
25 * require at least these expectations.
|
| /openbmc/linux/Documentation/process/ |
| H A D | code-of-conduct-interpretation.rst | 68 secondary by the expectations of contributors and maintainers.
70 Both the expertise expectations and decision-making are subject to
76 As a consequence, setting expertise expectations, making decisions and
|
| /openbmc/linux/include/net/netfilter/ |
| H A D | nf_conntrack_expect.h | 3 * connection tracking expectations.
79 /* Allow to reuse expectations with the same tuples from different master
|
| /openbmc/phosphor-ipmi-flash/tools/test/ |
| H A D | tools_pci_unittest.cpp | 291 /* Create expectations on pciMock for finding device and mapping memory region
408 /* Only set standard expectations; not those from nuvotonDevice */ in TEST()
440 /* Only set standard expectations; not those from nuvotonDevice */ in TEST()
459 /* Only set standard expectations; not those from nuvotonDevice */ in TEST()
483 /* Only set standard expectations; not those from nuvotonDevice */ in TEST()
515 /* Only set standard expectations; not those from nuvotonDevice */ in TEST()
563 /* Only set standard expectations; not those from nuvotonDevice */ in TEST()
|
| /openbmc/linux/net/netfilter/ |
| H A D | nf_conntrack_expect.c | 227 /* delete all expectations for this conntrack */
239 hlist_for_each_entry_safe(exp, next, &help->expectations, lnode) { in nf_ct_remove_expectations()
296 * conntracks. During the conntrack destruction, the expectations are
405 hlist_add_head_rcu(&exp->lnode, &master_help->expectations); in nf_ct_expect_insert()
415 /* Race with expectations being used means we could have none to find; OK. */
422 hlist_for_each_entry(exp, &master_help->expectations, lnode) { in evict_oldest_expect()
|
| /openbmc/linux/net/ipv4/netfilter/ |
| H A D | nf_nat_h323.c | 187 /* Set expectations for NAT */ in nat_rtp_rtcp()
212 /* Run out of expectations */ in nat_rtp_rtcp()
214 net_notice_ratelimited("nf_nat_h323: out of expectations\n"); in nat_rtp_rtcp()
289 /* Set expectations for NAT */ in nat_t120()
328 /* Set expectations for NAT */ in nat_h245()
407 /* Set expectations for NAT */ in nat_q931()
489 /* Set expectations for NAT */ in nat_callforwarding()
|
| /openbmc/linux/lib/kunit/ |
| H A D | kunit-example-test.c | 14 * makes a set EXPECTATIONs and ASSERTIONs about the behavior of some code; if
15 * any expectations or assertions are not met, the test fails; otherwise, the
26 * to test a piece of code, you set some expectations about what the in example_simple_test()
|
| /openbmc/linux/net/netfilter/ipvs/ |
| H A D | ip_vs_nfct.c | 21 * - FTP support (NAT), ability to support other NAT apps with expectations
22 * - to correctly create expectations for related NAT connections the proper
151 * expectations even if they use wildcard values, now we provide the in ip_vs_nfct_expect_callback()
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Configuration/ |
| H A D | README.md | 4 expectations we typically use elsewhere in this repository. Any types and
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | rpolicy.md | 7 use those methods can be configured based on system expectations.
|