CppCon, October 2023 Why Loops EndNo. 1The heat death of the universe👿 👿 😈 Will this loop ever end? 🙂 Yes! Execution increases the entropy of the universe, turning free energy into useless thermal specific? 😈 Will this loop end for some non-cosmological reason?🙂 That is very specific! But you’ll have to explain the part about the function interfaces. 😈 Will this loop end for some reason that: the bottom part of the interface.😈 Let’s call that sort of reason a local reason. Does the loop end for some local reason? 🙂 OK, now there's a local reason. 😈 Now can you write it in a way my robot

cppcon_add_library(basic LIBRARIES Asio::asio) add_subdirectory(tests)

with Approval Tests Clare Macrae (She/her) clare@claremacrae.co.uk 16 September 2020 CppCon (Online)2 Audience: Developers testing Desktop GUIs, including Qt-based ones Approval Tests: claremacrae tations.html3 Contents •Introduction •Qt –Setting Up Testing –Error-prone Things –Approval Tests •Extras –Tools –Summary4 About Me • Scientific C++ and Qt developer since 1999 • My mission: mission: Sustainable and efficient testing and refactoring of legacy code – Co-author of “Approval Tests for C++” • Consulting & training via “Clare Macrae Consulting Ltd” – claremacrae.co.uk • All links

API Tests Low Effort API Testing for Microservices | CONFIDENTIAL • What has changed? – Migration to microservices triggering need for extensive API tests • Problem: – Creating API tests is effort effort intensive – Creating + maintainting E2E, service tests, component tests adds up very quickly • What happens if you do not address the problem? – Thorough test coverage can take a lot of time outcome: Just create E2E tests • What is our solution? – Leverage Istio sidecar to listen to API traffic data and create tests from the data – 10x speed in creating API tests • Can also be sped up

Behavior-driven Tests for Microservices-based Algo Trading System Summary : Introduction : This poster will introduce a test framework we use at Bloomberg to enable behavior-based tests in natural language often non-trivial to automate the system-level tests with external dependencies. Controlling external dependencies are especially important for algo tests since certain algo behaviors require hard-to-produce a test framework is proposed to address these pain points: ● End-to-end : The test framework validates the end (client) to end (broker/exchange) algo behavior. ● Controlled external dependencies

@import("std").debug.assert; test "comments" { // Comments in Zig start with "//" and end at the next LF byte (end o // The below line is a comment, and won't be executed. //assert(false); = true; // another comment assert(x); } $ zig test comments.zig Test 1/1 comments...OK All tests passed. There are no multiline comments in Zig (e.g. like /* */ comments in C). This helps allow assert(null_terminated_bytes[5] == 0); } $ zig test test.zig Test 1/1 string literals...OK All tests passed. See also: Arrays Zig Test Source Encoding Escape Sequences Escape Sequence Name \n Newline

expect = @import("std").testing.expect; test "comments" { // Comments in Zig start with "//" and end at the next LF byte // The below line is a comment, and won't be executed. //expect(false); true; // another comment expect(x); } $ zig test comments.zig 1/1 test "comments"... OK All 1 tests passed. There are no multiline comments in Zig (e.g. like /* */ comments in C). This helps allow expect(mem.eql(u8, "hello", "h\x65llo")); } $ zig test test.zig 1/1 test "string literals"... OK All 1 tests passed. See also: Arrays Zig Test Source Encoding Escape Sequences Escape Sequence Name \n Newline

@import("std").debug.assert; test "comments" { // Comments in Zig start with "//" and end at the next LF byte (end o // The below line is a comment, and won't be executed. //assert(false); true; // another comment assert(x); } $ zig test comments.zig 1/1 test "comments"...OK All tests passed. There are no multiline comments in Zig (e.g. like /* */ comments in C). This helps allow assert(null_terminated_bytes[5] == 0); } $ zig test test.zig 1/1 test "string literals"...OK All tests passed. See also: Arrays Zig Test Source Encoding Escape Sequences Escape Sequence Name \n Newline

assert = @import("std").debug.assert; test "comments" { // Comments in Zig start with "//" and end at the next LF byte // The below line is a comment, and won't be executed. //assert(false); true; // another comment assert(x); } $ zig test comments.zig 1/1 test "comments"...OK All 1 tests passed. There are no multiline comments in Zig (e.g. like /* */ comments in C). This helps allow assert(mem.eql(u8, "hello", "h\x65llo")); } $ zig test test.zig 1/1 test "string literals"...OK All 1 tests passed. See also: Arrays Zig Test Source Encoding Escape Sequences Escape Sequence Name \n Newline

expect = @import("std").testing.expect; test "comments" { // Comments in Zig start with "//" and end at the next LF byte // The below line is a comment, and won't be executed. //expect(false); another comment try expect(x); } $ zig test comments.zig Test [1/1] test "comments"... All 1 tests passed. There are no multiline comments in Zig (e.g. like /* */ comments in C). This helps allow non-UTF-8 strings are possible } $ zig test test.zig Test [1/1] test "string literals"... All 1 tests passed. See also: Arrays Zig Test Source Encoding Escape Sequences Escape Sequence Name \n Newline