[SciPy-dev] Add bz2 support to io.mmio [not tested] <--
Thu Apr 10 12:45:36 CDT 2008
On Thu, Apr 10, 2008 at 8:41 AM, Pearu Peterson <email@example.com> wrote:
> > I appreciate that you labelled the test deficiency, but what now? Are
> > you going to add the test, or was the message meant as a reminder to
> > someone else?
> Have you followed the thread
> ? The changeset is there because a user asked a feature. Adding
> this feature was trivial, testing it is not so because it requires certain
> input that I don't have at hand. There is a request for the user to check
> if the feature works.
> I don't see harm in such patches, it does not break anything,
> and there is potential user who can confirm if the feature works or not.
I haven't talked with Stefan about this, but I believe that his point
(or at least this is my point) is not whether this code is fully
tested in the sense that the code is correct. I think the issue is
that we are requiring unittests; that is, there should be a short
little unittest added here:
I also agree that adding simple features such as this to satisfy user
requests is very good. I spoke up about this because I think this a
really important general discussion and isn't exclusively related to
this specific check-in. Obviously, adding features will often require
having user's test these features to ensure that they perform as
specified. But it is essential that we have extensive unittests so
that when we edit and change code, there is some mechanism available
to determine whether old code is broken (hopefully, with a
The solution to this problem shouldn't be that Stefan monitors add new
code to determine whether it comes with unittests or not. He
shouldn't have to write the unittests himself and he shouldn't have to
create a ticket every time someone checks in un(unit)tested code.
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
More information about the Scipy-dev