performance, we typically think about the function logic. We’ll see that a well designed function API can have an even larger impact.How will we compare performance? ● Benchmarks at this low level are advance(RandIter& iter, Diff n, random_access_iterator_tag) { iter += n; } ● Access token to make some API available only inside the library (like the default “package private” access modifier in Java) Empty

the important data structures and concepts? Prior work in the GraphBLAS community, C API Overview of our draft C++ API How might this interoperate with standard C++, graph library proposal? 4[DISTRIBUTION the important data structures and concepts? Prior work in the GraphBLAS community, C API Overview of our draft C++ API How might this interoperate with standard C++, graph library proposal? 5[DISTRIBUTION the important data structures and concepts? Prior work in the GraphBLAS community, C API Overview of our draft C++ API How might this interoperate with standard C++, graph library proposal? 6[DISTRIBUTION

TestCalcEngine TestCalcEngine MOCK_METHOD(bool, execute, (...), (override)); MOCK_METHOD(bool, apply, (...), (override)); MOCK_METHOD(bool, calculate, (), (override)); MOCK_METHOD(bool, apply, (...), (override));Create calculate(const Data& rdata); }; struct TestCalcEngine { TestCalcEngine(); MOCK_METHOD(bool, apply, (const Data&)); MOCK_METHOD(bool, calculate, (const Data&)); }; Injection DependencytemplateMOCK_METHOD(bool, apply, (const Data&)); MOCK_METHOD(bool, calculate, (const Data&)); }; template concept CalcEngineT

daunting so it's easier to have a global grab bag • Other user groups using a long established API in legacy codebase are unwilling to change their function calls • Efficiency, I only create one std::endl; // Further validation of rec values ... }class MockClient : public CommWrapper { public: MOCK_METHOD1(send, Response(const Request&)); }; Bloomberg 20 TEST(XTest, sendData) { MockClient a_client; }; struct Service { static CommWrapper comm_; }; Bloomberg 23 Modern C++struct MockClient { MOCK_METHOD1(send, Response(Request)); Response operator()(Request req) { return send(std::move(req));

path_generator_service_; }; ● PathGenerator inherits from rclcpp::Node making it inextricably linked to the ROS 2 API ● set_map_service and generate_path_service are callback functions that run when requests are sent path_generator_service_; }; ● PathGenerator inherits from rclcpp::Node making it inextricably linked to the ROS 2 API ● set_map_service and generate_path_service are callback functions that run when requests are sent path_generator_service_; }; ● PathGenerator inherits from rclcpp::Node making it inextricably linked to the ROS 2 API ● set_map_service and generate_path_service are callback functions that run when requests are sent

(Try to mock as little as possible)How Hardware tests should look like Init Write Read ComparePrepare dataInitWriteReadCompareHighly Effective: ⊡ Testing customer interfaces ⊡ Exemplary API usageHighly usageHighly Effective: ⊡ Testing customer interfaces ⊡ Exemplary API usageHighly Effective: ⊡ Testing customer interfaces ⊡ Exemplary API usageMotivation for layer separation: ⊡ Simplifies testing ⊡ Promotes

connection attempt is made. Then error code ETOOMANY is returned.UNIT TESTS Test a module in isolation. ‘Mock’ interfaces to other modules / system. Bugs are generally shallow / easy-to-fix. Tests run fast #include class MockFS : public FS { public: MOCK_METHOD(int, read, (int fd, void*buf, size_t len), (override)); MOCK_METHOD(int, write, (int fd, const void *buf, size_t len), (override));

reading • Ability to add diagnostics • Reduce locations where variable is changed • Ability to mock or override reads/writes • Prevent proliferation to other files void SetNextWindow(Window nextWindow); cppAnd what does this gain us? • Single path for external and internal callers • Dogfooding public API • Changes to logic occur in one location • Ability to override for testing void VHFDevice::NewPacketCallback

under test fails, and for no other reason" -- Titus Winters 28Option 1: Isolation Unit Testing: Mock the external thing Create the external thing as part of the test (forking a process to open a socket)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3 New public Python API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.4 New build multiple auth protocols (LDAP), Virtual and Remote repositories to create advanced topologies, a Rest API, and generic repositories to host any artifact. • The conan_server is a small server distributed together reference is the source of truth for the interfaces of every public command, class, method, helper, API and configuration file that can be used. It is not designed to be read fully, but to check for individual