I'll echo exactly what Ben has said. Automated tests are great, when there are a lot of people working on something, or when it is a big company and there's a codebase that has matured. If you're building something with a couple of people or by yourself, I'd say don't focus on tests. Add some tests for any business critical parts that would be disastrous if it breaks, or as you're fixing bugs maybe add some tests (test to prove it's broken, and validate it is fixed with your change).
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.
I'll echo exactly what Ben has said. Automated tests are great, when there are a lot of people working on something, or when it is a big company and there's a codebase that has matured. If you're building something with a couple of people or by yourself, I'd say don't focus on tests. Add some tests for any business critical parts that would be disastrous if it breaks, or as you're fixing bugs maybe add some tests (test to prove it's broken, and validate it is fixed with your change).