Message165200
| Author |
r.david.murray |
| Recipients |
chris.jerdonek, ezio.melotti, orsenthil, r.david.murray |
| Date |
2012年07月10日.20:04:01 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1341950643.41.0.357426715712.issue15302@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
As mentioned, the first step is to create some tests that can validate the current behavior, so that changes don't break things. This is a non-trivial task. I know from experience with a similar refactoring that even seemingly simple changes can have unexpected consequences, and that getting good functional test coverage (not code-line test coverage) is hard. This is complicated by the fact that regrtest is an over-evolved mess. My ideal is to move appropriate pieces of the functionality into unittest and make regrtest a wrapper around that, but obviously I haven't spent much time actually doing that.
I don't think that regrtest tests need to be run as part of the standard python test run, by the way, though I suppose they could be. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年07月10日 20:04:03 | r.david.murray | set | recipients:
+ r.david.murray, orsenthil, ezio.melotti, chris.jerdonek |
| 2012年07月10日 20:04:03 | r.david.murray | set | messageid: <1341950643.41.0.357426715712.issue15302@psf.upfronthosting.co.za> |
| 2012年07月10日 20:04:02 | r.david.murray | link | issue15302 messages |
| 2012年07月10日 20:04:01 | r.david.murray | create |
|