English lad currently a C#/Java/VueJs/JavaScript/TypeScript engineer.
Extra dribbling can be found at https://codeheir.com
Portfolio found at https://lukegarrigan.com
I follow uncle bobs rules for writing tests; the 3 laws of TDD:
You are not allowed to write any production code unless it is to make a failing unit test pass.
You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
Also, you said "I noticed that reduced a lot when working on static type languages." When writing tests in dynamically typed languages you shouldn't be testing for types so really you should be writing an equivalent amount of tests. But I know this goes on, I've seen countless applications where people have written tests in dynamically typed languages like: "What happens if I put a string in here? ahh okay, now what happens if I put an int in here", this shouldn't happen.
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.
I follow uncle bobs rules for writing tests; the 3 laws of TDD:
Also, you said "I noticed that reduced a lot when working on static type languages." When writing tests in dynamically typed languages you shouldn't be testing for types so really you should be writing an equivalent amount of tests. But I know this goes on, I've seen countless applications where people have written tests in dynamically typed languages like: "What happens if I put a string in here? ahh okay, now what happens if I put an int in here", this shouldn't happen.