Skip to main content
added 17 characters in body
Source Link
Robert Harvey
  • 200.7k
  • 55
  • 470
  • 683

Should you write tests is what iI heard you asking?

Well, why do we write tests? To deriskreduce risk! If we want to deriskreduce the risk of certain scenarios from happening it is best to write a test.

So if you think that there are not enough tests surrounding the new feature, please write tests.

But don't just write tests, and if they all pass then commit and push. You want to see the test fail, then add the code to make it pass, so you are EXACTLY sure you are fixing that one test. Also if you don't see the test fail, you could just be writing tests that don't actually test anything and might always pass.

Should you write tests is what i heard you asking?

Well, why do we write tests? To derisk! If we want to derisk certain scenarios from happening it is best to write a test.

So if you think that there are not enough tests surrounding the new feature, please write tests.

But don't just write tests, and if they all pass then commit and push. You want to see the test fail, then add the code to make it pass, so you are EXACTLY sure you are fixing that one test. Also if you don't see the test fail, you could just be writing tests that don't actually test anything and might always pass.

Should you write tests is what I heard you asking?

Well, why do we write tests? To reduce risk! If we want to reduce the risk of certain scenarios from happening it is best to write a test.

So if you think that there are not enough tests surrounding the new feature, please write tests.

But don't just write tests, and if they all pass then commit and push. You want to see the test fail, then add the code to make it pass, so you are EXACTLY sure you are fixing that one test. Also if you don't see the test fail, you could just be writing tests that don't actually test anything and might always pass.

Source Link

Should you write tests is what i heard you asking?

Well, why do we write tests? To derisk! If we want to derisk certain scenarios from happening it is best to write a test.

So if you think that there are not enough tests surrounding the new feature, please write tests.

But don't just write tests, and if they all pass then commit and push. You want to see the test fail, then add the code to make it pass, so you are EXACTLY sure you are fixing that one test. Also if you don't see the test fail, you could just be writing tests that don't actually test anything and might always pass.