Write tests #6

eads opened this Issue Nov 21, 2012 · 2 comments


None yet

3 participants

eads commented Nov 21, 2012

I need to brush up on writing Django tests.

@eads eads was assigned Nov 21, 2012
@codersquid codersquid was assigned Dec 22, 2012
ghing commented Mar 19, 2013

It might be useful to generate a fixture using the dumpdata management command to bootstrap the test database for testing the various Resource classes.

Should the data be sanitized? I'm not sure how I feel about people's inmate admission records living forever in a git repo history. In the past, I've written a script using the name_generator package to replace real names with random ones.

Finally, the data set is big and slicing it/anonymizing it might be a little bit cumbersome or time consuming. It's probably a good idea to start writing some (failing) tests to get a better sense of what should be in the fixtures.

eads commented Jul 30, 2013

This needs to become part of our practice and we need specific tickets.

To address @ghing's comments from way back, we don't track any names nor do we keep the DOB (just the age at booking), so there's very little to identify people once they've dropped out of the system.

@eads eads closed this Jul 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment