I’m sure we have all encountered the situation where supposedly-helpful automated user-interface tests become a weight which drags down the agility of a project. The usual upshot of this is that either the project stops being “agile” or the offending tests are “temporarily” bypassed, and never run again.
Manish Kumar has written an article about this: Agile Testing ,Lean principles: Why Testing is perceived as least agile: What needs to change
Interestingly, in his choice of solutions he does not include my personal favourite – writing/changing the tests before implementation, and letting the new tests be the specification for the work to be done. This way the effort of changing the tests is in itself valuable, particularly as it might lead to a reduction in excess documentation of specifications before work can start.