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
The purpose of unit tests is not really to check correctness at t=0, which is low-value and can be done via other means. It is to avoid future breakages and to be able to make changes with confidence. Write your tests with this in mind.
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.
Duty Now For the Future In so many things, Mothersbaugh saw...
The problem is not the 100% test coverage but what the people do to follow that policy such us wasting time in test that are not necessary or, what is worse, perform an "assertion free test" , that is, going through the code to get coverage without testing it correctly.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
