In test-driven development, should the developer write the tests?

Question

Test Driven Development

I am a tester and the task is to write autotests before the service that will have to be tested is implemented.

1. When developing through testing, does the developer necessarily write unit tests? Does the tester already cover the API with autotests from its functionality bell tower?

2. Is it realistic for a tester to write autotests for checking functionality during test-driven development?

Answer 1

A developer can (and even should) write tests, because he must submit a working code, and you can check whether the code works either by hand or by tests.
But it is not entirely clear where the developer has to do if the task was assigned to the testers. No problem. You have a spec, "when sending a request to such and such a URL, the service returns a response with such and such data." Well, express it in your test, sending a request to a URL that doesn't exist yet and validating the data in the response that doesn't exist yet.

Answer 2

The meaning of test-driven development is not in tests, but in development. You plan the development, but don't cover it with tests (bonus coverage). The tester will have to think over the key and critical points (routes, request types, parameters, response formats, etc.) that directly affect the development. This has nothing to do with testing. Direct development and design of the application in the front, which should be handled by the developer. About unit tests are generally nonsense, heresy and trolling.