Refactor without regret

Often, you're faced with the need to reuse or depend on existing code you didn't write. While there are valid reasons for this, it can come with drawbacks—especially in the form of technical debt. Today, technical debt stands as a significant barrier to further development. Reworking such code can introduce new bugs and potentially degrade or break existing functionality rather than improve it. This presentation outlines an automated process that leverages characterization testing, change-based test execution, static analysis, and data intelligence to systematically refactor code, with a focus on measuring and reducing technical debt.

Value for the audience:
Learn how characterization testing can serve as a reliable basis for reworking code that was previously insufficiently covered. Using the tests in a continuous environment with monitoring enables efficient and targeted refactoring.

Problems addressed:
Reducing Technical Debt in Legacy or Third Party Code

Continuous Monitoring of code changes in a CI/CD Environment

Talk language: English
Level: Advanced
Target group: Development Managers, Project Managers, Quality Managers

Company:
Vector Informatik GmbH

Dipl.-Inform. Andreas Horn