| ||
Fri 2024-04-19
Thu 2024-04-18
Mon 2024-04-15
Butterick’s Practical Typography Sat 2024-04-13
Fri 2024-04-12
Wed 2024-04-10
Boy Meets Boy Meets Boys’ Love Tue 2024-04-09
Mon 2024-04-08
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
When I'm looking at a new open source project one of the first
questions I ask is "how good is this software?". Unless
you know something about the reputation of the author or the code it
can be remarkably difficult to tell whether something is good or crap.
Caveat codor.
This is another reason why unit tests are so important. They're like a badge of quality. The fact that there are tests at all is a good sign. Run them, do they pass? Scan through the test code; does the coverage look good? The tests are usually a handy API example, too.  Mark and his feed parser are famous enough that I figured it was good quality code. But seeing 1882 tests pass sure is reassuring and it's quite interesting to read the tests. For the bad side of this see the tests for pywebsvcs. Many of the tests don't work last I looked. It's not clear which tests are even useful. I don't mean to slag the pywebsvcs developers — they're doing great work — but I'd sure feel better about the code if it had a test suite I understood. |
|
