Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

May want to create "unit testing" dataset on the Chicago data portal #45

Open
tomschenkjr opened this issue Jul 4, 2015 · 3 comments
Open

Comments

@tomschenkjr
Copy link
Contributor

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.

@tomschenkjr
Copy link
Contributor Author

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.

@tomschenkjr
Copy link
Contributor Author

@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.

@levyj
Copy link
Member

levyj commented Jun 6, 2019

It would, by definition, be private dataset, right? If so, I am not really concerned about clutter or user confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants