Course: Test-Driven Development (TDD) and Refactoring with C++ and C# · 2 days [D6]

Course: Test-Driven Development (TDD) and Refactoring with C++ and C# · 2 days [D6]

from 78.00

Learn how to design and code in C++ and C# using a test-driven development approach.

Duration: 2 days / 4 evenings / 14 hours
Audience: Developers, Development Leads, Test Developers, Scrum Masters
Certification: Upon training completion
Courseware licence: 3 months or perpetual

Learning cases and programming katas:
✓ Understand if TDD is a good investment
✓ Create code through small TDD iterations
✓ Develop unit and integration tests
✓ Decide when to refactor code
✓ Apply TDD for existing code
✓ Refactor code using patterns
✓ Collaborate with testers and BAs with low overhead
✓ Benefit from the xUnit test framework and productivity tools
✓ Apply continuous integration and smart change-based testing
✓ Use mocking and dependency injection

- View price at top after selecting Format / Public event
- For zone-dependent pricing, please select your zone
- For discounts and terms, please view pricing details

Format / Public event:
Add to cart & Register


1 · Design, Coding and Testing and Agile

  • Agile business value
  • Evolutionary design and development
  • The agile test quadrants
  • Cross-team collaboration and new testing ownerships
  • Continuous integration and the test automation paradigm shift
  • The need for refactoring and TDD


2 · Unit and Integration Test-Driven Development

  • Testing class behavior and using APIs
  • Source code analysis
  • Unit testing techniques and frameworks
  • Code refactoring techniques
  • Mock objects and dependency injection
  • Integration testing interfaces and collaborations
  • Integration testing techniques and frameworks

3 · Acceptance Test-Driven Development

  • Story acceptance criteria and tests
  • Developer role in acceptance testing
  • Acceptance testing with the FitNesse framework
  • Coding ATDD fixtures
  • Collaboration with testers and Product Owners

4 · Refactoring

  • Why refactor?
  • Technical debt
  • Code smells
  • Refactoring process
  • Refacoring techniques
  • Refactoring and tests


5 · Tools and Frameworks

  • Testing frameworks
  • Automation tools
  • Continuous integration environments
  • Static and dynamic testing tools
  • Refactoring tools

Seattle, San Francisco, Chicago, Boston, New York, Austin (USA) · Vancouver, Toronto, Montreal (Canada) · Mexico City (Mexico) · Rio de Janeiro, Sao Paulo (Brazil) · Santiago (Chile) · Stockholm (Sweden) · Copenhagen (Denmark) · Dublin (Ireland) · London (UK) · Paris, Toulouse, Lyon, Nice (France) · Amsterdam, Eindhoven (Netherlands) · Brussels (Belgium) · Berlin, Munich (Germany) · Helsinki (Finland) · Tallinn (Estonia) · Zurich (Switzerland) · Vienna (Austria) · Prague (Czech Republic) · Warsaw (Poland) · Milan Rome (Italy) · Barcelona, Madrid, Malaga (Spain) · Lisbon (Portugal) · Moscow, St Petersburg (Russian Federation) · Cape Town, Johannesburg (South Africa) · Nairobi (Kenya) · Tel Aviv (Israel) · Riyadh (Saudi Arabia) · Dubai (UAE) · Doha (Qatar) · Delhi, Pune, Hyderabad, Bengaluru (India) · Kuala Lumpur (Malaysia) · Singapore · Jakarta (Indonesia) · Ho Chi Minh City (Vietnam) · Seoul (South Korea) · Beijing, Shanghai (China) · Hong Kong · Tokyo (Japan) · Sydney, Melbourne (Australia) · Auckland (New Zealand)