Since Agile is iterative and many test-last tools are record and playback-style, and therefore can't really be applied in an Agile environment, this brings up a few issues.
- the target for test is changing, rapidly - making it very difficult to automate
- by the time the target code has settled, the sprint/iteration is over, and you're on to new tasks (at least in the PM/BA's mind)
- resource management is difficult - 'if project A is 'done' (shipped) why are you now doing automation for it' may be asked.
What strategy can be applied in an agile environment to ease the pain of these moving targets / project-resource misalignment?