What if we start their TDD experience with integration tests instead of unit
tests.
Provide them with the running skeleton that already has all dependencies like DB
running (e.g. in a container) and let them write tests against the public API.
A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
What if we start their TDD experience with integration tests instead of unit
tests.
Provide them with the running skeleton that already has all dependencies like DB
running (e.g. in a container) and let them write tests against the public API.
This would remove one of the pains in writing tests: mocking.