I usually write an implementation first, but when testing it i try to re-evaluate the requirements - i do not look at implementation at all. Test should handle

I usually write an implementation first, but when testing it i try to re-evaluate the requirements - i do not look at implementation at all. Test should handle all edge cases. And i do modify tests, because sometimes assumptions are wrong(or domain experts change their mind or got something wrong) Sadly functionality requirements are very soft in my industry(once it was requested from me to do a perfect fuzzy match..) Most of the time i am required to modify untested legacy code, that starts with test(if it is even possible).