Open aalex opened 3 years ago
It would definitely add value to the project if we would implement some tests, instead. I wouldn't remove those test boilerplate without checking with the Product Owner. My recommendation is indeed to use these stub to implement some, instead of removing the folder.
Each time we create a PR, Github would run our unit test suite to make sure that our generators - or whatever code we write test for - do work.
In lean software dev, we want a quick feedback loop. Write code -> write tests -> do the tests run ok? -> if not, fix it -> then ask for a code review. ->get some change requests -> do the requested changes -> once approved, merge it -> then some QA engineer tests it -> then demo it in a sprint review.
Maybe we should list what could benefit from unit tests:
Example:
As developers, we need unit, so that we know our code works.
Criteria
Details