Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #63004
| From | Roy Smith <roy@panix.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Score one for unit testing. |
| Date | 2014-01-02 17:53 -0500 |
| Organization | PANIX Public Access Internet and UNIX, NYC |
| Message-ID | <roy-88539A.17532802012014@news.panix.com> (permalink) |
We've got a test that's been running fine ever since it was written a month or so ago. Now, it's failing intermittently on our CI (continuous integration) box, so I took a look. It turns out it's a stupid test because it depends on pre-existing data in the database. But, the win is that while looking at the code to figure out why this was failing, I noticed a completely unrelated bug in the production code. See, unit testing helps find bugs :-)
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
Score one for unit testing. Roy Smith <roy@panix.com> - 2014-01-02 17:53 -0500 Re: Score one for unit testing. Chris Angelico <rosuav@gmail.com> - 2014-01-03 10:00 +1100
csiph-web