What does testing debt look like and how do you keep on top of it?

Tell me some stories about testing debt such as outdated scripts, unreviewed automation, hard-to-integrate new features, lack of unit tests and more.

Some questions that might spark thoughts around testing debt:

  • How do you stay up to date with your project deliverables?
  • How do you keep artefacts up-to-date?
  • Do you have a change control in place?
  • How do you capture and track changes to risks?
  • Do you delete/archive outdated artefacts?
  • How do you keep things lean?

With your experiences, Iā€™d like to know, what does testing debt look like, why does it happen and how do you keep on top of it?

2 Likes