4 ms·
These are minor inconveniences relative to the massive benefits all these techniques bring to your codebase. "Go to implementation" shortcut is a thing and solv
by Toine 5y ago
These are minor inconveniences relative to the massive benefits all these techniques bring to your codebase. "Go to implementation" shortcut is a thing and solves the first 2.
"One assert per test" -> just test one "concept" per test, not literarily 1 assert statement per test. IE :
assert(loc.x == 10.3)
assert(loc.y == 10.4)
assert(loc.z == 10.5)
is absolutely fine (even you could do it in 1 assert).
- pydry 5y agoIf he meant one "concept" he probably would have said that. In any case, "concept" being such a loosely defined thing would render the rule a bit pointless. There is something deeper behind this rule but think he fucked up articulating what it was.