Legacy software often comes with technical debt that was built up over the years. That debt could be a lot of badly implemented manual tests or instable automated tests which all have to be executed for releasing new versions of the software. Fixing this technical debt is a difficult task and it is sometimes hard to figure out where to start. This paper shows guidance on how to escape that tricky situation. The paper presents patterns on how to organize system tests and on how to focus the workforce on tackling that technical debt bit by bit for building up daily running and stable system tests.

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

Patterns for Fixing Instable Legacy System Tests

  • Christopher Preschern

摘要

Legacy software often comes with technical debt that was built up over the years. That debt could be a lot of badly implemented manual tests or instable automated tests which all have to be executed for releasing new versions of the software. Fixing this technical debt is a difficult task and it is sometimes hard to figure out where to start. This paper shows guidance on how to escape that tricky situation. The paper presents patterns on how to organize system tests and on how to focus the workforce on tackling that technical debt bit by bit for building up daily running and stable system tests.