We add comments most of the time. Maybe it's a bit OCD but we like it that way.
We separate unit and integration tests into 2 different libraries, as running integration tests is less frequent than running unit tests.
The naming convention is fine. But we don't write should as the unit does something. e.g GetValue_WhenGivenNumberIs3_ReturnsFizz()
GetValue_WhenGivenNumberIs3_ReturnsFizz()
The sooner you involve the younger/new devs in unit testing it will serve the team in the long run. Go for it :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
We add comments most of the time. Maybe it's a bit OCD but we like it that way.
We separate unit and integration tests into 2 different libraries, as running integration tests is less frequent than running unit tests.
The naming convention is fine. But we don't write should as the unit does something.
e.g
GetValue_WhenGivenNumberIs3_ReturnsFizz()The sooner you involve the younger/new devs in unit testing it will serve the team in the long run. Go for it :)