One thing that I have always noticed in my unit tests is that they become kind of verbose; Seeing that they may also not be detailed enough, how do you know when your unit tests are the right size?
I know a good quote for this, and this:
"Perfection is achieved, not when there is nothing to add, but when there is nothing that could be removed." - Antoine de Saint-Exupery.
, , , . unit test , . , , . , , unit test, .
, , , /, , , ( ).
, unit test , . , , , . , , , .
, , . 100 , , , , , .
, , , , .
Edit In response to your editing: I'm not looking for excellence in unit tests.
Source: https://habr.com/ru/post/1745341/More articles:How to use default arguments in php - phpThe safest way to idle a delphi application to wait for a timer? - memory-managementBing search API using Jsonp does not work, invalid label - jsonHow to find out if your Unit Test Fixture is right? - language-agnosticHow to replace a UITableViewController with a UIViewController that contains a UITableView? - cocoa-touchHow do I take pairs from a list in python? - pythonКак изменить исходный HTML-страницы ASP.NET на PreRender? - asp.netHow to use NSPredicate for Key-Path values - objective-cIEnumerable, представляющий "остаток" последовательности IEnumerable - linked-listAny tools out there that will be EXECUTE BPMN 2.0 xml code yet? - xmlAll Articles