Personally, what did it for me was looking at tests as canvases or scratchpads for my application and not worrying about doing things "right" from the minute I write that first line of code. I don't worry about proper names or abstractions until I'm in the refactor stage of the TDD cycle, and even then, it's a very iterative approach.
I highly recommend a video called Play by Play: TDD with Brad Wilson if you can still find it online. It shows this approach quite well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Personally, what did it for me was looking at tests as canvases or scratchpads for my application and not worrying about doing things "right" from the minute I write that first line of code. I don't worry about proper names or abstractions until I'm in the refactor stage of the TDD cycle, and even then, it's a very iterative approach.
I highly recommend a video called Play by Play: TDD with Brad Wilson if you can still find it online. It shows this approach quite well.