C++ Unit Testing with Refactoring
TDD in C++: Writing code test first with automated tests
TDD and refactoring are key skills for C++ teams looking to undertake Agile Software Development.
Teams practising TDD in C+ can expect significantly lower defect count and consequently shorter, more predictable, schedules and happier customers. Automated test first development reduces the space in which bugs can hide.
- 2 days hands-on workshop.
- Optional day add-on to provide extra time with exercises / to look at code and discuss legacy issues.
A test-driven approach, in which design is grown and code delivered incrementally according to functionality or risk, forms the basis of the construction phase of an iterative and incremental development. The use of unit testing provides confidence in existing code and supports the ability to refactor code as development unfolds.
About this course
The Test-Driven Development in C++ course presents a number of modern practices for developing code based on an adaptive development life cycle. Agility and predictability are two qualities often missing from software development.
The course is intended as a practical course: the best way to appreciate how test-driven development works and what it feels like is to do it in practice, making sense of the principles item bodies. In this form the course is based on lecture material, demonstration, discussion, exercises and hands-on labs.
Who should attend?
The course is suitable for software developers experienced in C++ and familiar with object-oriented principles and practices. Any previous exposure to unit testing or Agile development concepts is beneficial but not essential.
What Will I learn?
- Appreciate the benefits of testing as a design tool and not just a defect reduction technique.
- Recognise the purpose and practice of refactoring in keeping a system supple and adaptable.
- Know how to build up a set of unit tests.
- Understand the consequences of dependency management on testing and code quality.
- Programmer Testing Evidence of care: Testing viewpoint, Pragmatic testing, Automation, Bug pathology and Testing frameworks.
- Good Unit Tests Test quality: Good unit tests (GUTs), Not-so-good unit tests, Fine-grained tests, Behavioural tests, Functional versus operational testing and Black-box tests.
- Overview of xUnit xUnit and the xUnit family: Tests in xUnit, xUnit assertions, Testing thrown exceptions, other xUnit features and Organising xUnit tests (please see below for other test frameworks).
- Testing Approach Testing sensibility: passive, reactive, active, Plain Ol’ Unit Testing (POUT), Defect-Driven Testing (DDT), Test-Driven Development, Key TDD practices, The test-first cycle and Definition of done.
- More GUTs Cohesive and focused tests: Propositional test names, Example-based tests, Choosing example data, Quality of failure, What to include and exclude, Short test cases, Single level of abstraction and Anatomy of a test case (Given – When – Then).
- Listening to Your Tests Feedback from testing: Reasons testing can be hard, Technical debt, Classifying and reacting to technical debt, White-box testing issues and Coverage.
- Refactoring Kinds of changes to code, Code smells: Dimensions of change, Elements ofrefactoring, Some common refactorings and Refactoring motivation and applicability.
- Test-Driven Decoupling Unit testability and coupling: Unmanaged dependencies, External dependencies, Unit versus integration tests, Characterising testability, Singletons and statics,Test doubles and Doubling techniques in C++.