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

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 condition. ● Fully automated : Running tests are integrated into CI so algo behaviors are regressed for any dependent code change. ● Natural language layer: Tests are written in natural language so

and Mike Shah (tomorrow): Back To Basics, Debugging and Testing Chip Hogg (Wednesday), Making Hard Tests Easy (Robotics Track) Xiaofan Sun (Thursday): Mix Assertion, Logging, Unit Testing and Fuzzing Pete 3Learning Unit Testing CppCon 2015: T. Winters & H. Wright “All Your Tests are Terrible..." 4Rule 0 Write unit tests 5Part 0: Basics of the Basics Unit testing is the act of testing the correctness correctness of your code at the smallest possible unit: the function. Unit tests are small, automated, stand alone executables that perform unit testing on your code. Part 0: Basics 6auto abs(int x) ->

Google Test filter = FifoTest/0.* [==========] Running 6 tests from 1 test suite. [----------] Global test environment set-up. [----------] 6 tests from FifoTest/0, where TypeParam = Fifo1 [ RUN (0 ms) [----------] 6 tests from FifoTest/0 (0 ms total) [----------] Global test environment tear-down [==========] 6 tests from 1 test suite ran. (0 ms total) [ PASSED ] 6 tests.16 cfrasch@Charles- Google Test filter = FifoTest/0.* [==========] Running 6 tests from 1 test suite. [----------] Global test environment set-up. [----------] 6 tests from FifoTest/0, where TypeParam = Fifo1 [ RUN

Ruth (he/him) brian.ruth@garmin.comPart 0: Legacy Code• It works* • It may not have tests, but has been tested • Documents all the decisions and problems encountered in its lifetime • It every feature Write Automated tests and run them continuously Test the change you just made Testing StrategiesTest Everything on every feature Write Automated tests and run them continuously Test every feature Write Automated tests and run them continuously Test the change you just made Testing StrategiesTest Everything on every feature Write Automated tests and run them continuously Test

application __init__.py admin.py models.py migrations.py tests.py views.py static/ manage.py project.db requirements.txt 3.2.2. Add it to use reverse() [https://docs.djangoproject.com/en/2.2/ref/urlresolvers/#django.urls.reverse] in your tests, or test templates that use the url [https://docs.djangoproject.com/en/2.2/ref/templates/builtins/#std:templatetag- need to hook up your app to a special test version of urls.py and tell your tests to use that. So you could create myapp/tests/urls.py with the following code: from django.contrib import admin from django

application __init__.py admin.py models.py migrations.py tests.py views.py static/ manage.py project.db requirements.txt 3.2.2. Add it to use reverse() [https://docs.djangoproject.com/en/2.2/ref/urlresolvers/#django.urls.reverse] in your tests, or test templates that use the url [https://docs.djangoproject.com/en/2.2/ref/templates/builtins/#std:templatetag- need to hook up your app to a special test version of urls.py and tell your tests to use that. So you could create myapp/tests/urls.py with the following code: from django.contrib import admin from django

polls_cms_integration/ # the newly-created application __init__.py admin.py models.py migrations.py tests.py views.py static/ manage.py project.db requirements.txt Add it to INSTALLED_APPS Next is to integrate in your tests, or test templates that use the url template tag, you need to hook up your app to a special test version of urls.py and tell your tests to use that. So you could create myapp/tests/urls.py re_path(r'^myapp/', include('myapp.urls')), re_path(r'', include('cms.urls')), ] And then in your tests you can plug this in with the override_settings() decorator: from django.test.utils import override_settings

polls_cms_integration/ # the newly-created application __init__.py admin.py models.py migrations.py tests.py views.py (continues on next page) 16 Chapter 4. Software version requirements and release notes in your tests, or test templates that use the url template tag, you need to hook up your app to a special test version of urls.py and tell your tests to use that. So you could create myapp/tests/urls.py re_path(r'^myapp/', include('myapp.urls')), re_path(r'', include('cms.urls')), ] And then in your tests you can plug this in with the override_settings() decorator: from django.test.utils import override_settings