You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
This is why you should always seek to get to 100% test coverage, even if you are quite sure your current code is safe and well-written. In a project with hundreds of developers, you can't know what that code will look like in 3 years.
There is no such thing as a superfluous test. You are testing against unknown unknowns. Against the far future. Against other people. Etc. You should never make any assumptions about what needs testing and what doesn't.
The return-on-investment of a unit test only goes up as a function of time elapsed and number of changes made. For a long-running project, it's the most valuable code you will ever write.
In a world without deadlines, this would be true. In reality, we have to assess risk in various areas of our code and apply our limited testing resources accordingly. I've seen codebases with 100% coverage achieved mostly via unit testing which fail to test crucial scenarios.
I've also seen teams waste huge amounts of time unit testing trivial pieces of code at the expense of more significant tests. And then unit testing implementation details, which creates a lot of friction when it's time to refactor. Testing is not as simple as "test everything".
You can spend so much time obsessively writing tests that forward progress on product code slows to a crawl. Balance in everything...
You are basically protecting some function with your tests. That can also be a cost. In a fresh project I mostly avoid testing internals separately, as I don’t trust them to be the perfect abstractions.
Disagree. You should test the underlying functionality that matters. This mitigates tech debt over time, and, more importantly, keeps testing in high regard; a repo of 500 respected tests is taken care of, whereas a repo of 5000 aimless tests invites disregard and carelessness.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
