If a team has no automated tests, it's hard to get started
If a team has no automated tests, it's hard to get started. Why? Because there are many decisions to make:
Testing lib
Where to store tests
Mocking
CI config
Code coverage
etc.
The solution: Write one test.
Once one test exists, the team is highly likely to write more.
And yes, that first test may not make all the right decisions.
That's okay.
It's a starting point. It starts a conversation. It gives the team something to iterate upon. It conveys a path forward.
Related story:
I join a team that is behind schedule. Their app has no automated tests. So I write a few. They ask me to delete them. Why? Because they haven't picked a testing tech yet.
Don't let a perfect be the enemy of good. Some tests are better than nothing.