Comment Test first (Score 1) 308
Tell whoever's in charge that you need to add tests before you start making changes to the code, to ensure that any changes you make don't break existing functionality. Ask them if there are any specifications, requirements documents, or plans you can use to decide what tests to write. If they agree, lock down the existing behavior with tests, then use the tests as guidance when you enhance/refactor/rewrite the existing code. Test writing IS development -- it's building a scaffolding around the application you're developing, to ensure that the building doesn't fall when you add another story.
If they don't agree, ask them to tell you in writing that you should not write tests first and that they accept and take responsibility for the consequences of not adding tests.