Chicago
May want to create "unit testing" dataset on the Chicago data portal
For discussion...
The unit testing section of this package uses a number of datasets, such as Socrata's USGS Earthquake dataset, some city datasets, and others. However, we cannot adequately control the fidelity of the dataset which will introduce false-fails or otherwise mislead the integration process. We may want to consider creating a controlled dataset with known, static conditions to conduct unit testing.
This has been open for awhile, but am closing it because mixing "unit test" data with actual data will prove confusing to the user and clutter the city's data portal.
@nicklucius @geneorama - you guys are getting slammed with unit testing issues caused by changes made by @socrata. I wanted to re-raise this potential issue as a potential solution. It is less-desirable (see above thread), but could reduce the bi-weekly fire-drills. If Socrata continues to be unresponsive, may want to seriously consider this.
It would, by definition, be private dataset, right? If so, I am not really concerned about clutter or user confusion.
