<br><font size=2 face="sans-serif">I agree. </font>
<br><font size=2 face="sans-serif"><br>
Alan</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Ted Ralphs <tkralphs@lehigh.edu></b>
</font>
<br><font size=1 face="sans-serif">Sent by: coin-discuss-bounces@list.coin-or.org</font>
<p><font size=1 face="sans-serif">04/06/2005 02:37 PM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
Discussions about open source software for Operations Research
<coin-discuss@list.coin-or.org></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Discussions about open source software
for Operations Research <coin-discuss@list.coin-or.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: Unit test requirements (was Re:
[Coin-discuss] OsiCbc)</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Brady Hunsaker wrote:<br>
> Without commenting on the specific issues below, I'd like to suggest
<br>
> that we form a group of interested OSI developers to try to more <br>
> carefully specify expected OSI behavior and design the unit test <br>
> accordingly. The issues in this email need to be resolved, as
do some <br>
> that have come up in the past.<br>
> <br>
> As maintainer of OsiGlpk I have never been too careful about the unit
<br>
> test for these reasons. If we put some thought into clarifying
the <br>
> behavior we want, then we can write it down for developers and adjust
<br>
> the unit test accordingly so that it is more useful and all interfaces
<br>
> regularly pass the unit test. I think that will help OSI a great
deal.<br>
> <br>
> What do you think of creating such written guidelines for OSI behavior?
<br>
> I'm happy to be part of the group, though I would prefer that
someone <br>
> with broader OSI experience take the lead.<br>
<br>
A mailing list for the OSI is probably appropriate. I think written <br>
documentation is a good goal, but realistically, it's easier (and <br>
perhaps better) just to say that the expected behavior for an interface
<br>
is simply that it pass the unit test. If we design and comment the unit
<br>
test carefully, then any deviations from the required behavior will be
<br>
easy to understand and fix. This way, we don't have to try to keep the
<br>
documentation in sync with the unit test if we make changes. What do you
<br>
think?<br>
<br>
Cheers,<br>
<br>
Ted<br>
-- <br>
Dr. Ted Ralphs<br>
Assistant Professor<br>
Industrial and Systems Engineering<br>
Lehigh University<br>
(610)758-4784<br>
tkralphs@lehigh.edu<br>
www.lehigh.edu/~tkr2<br>
_______________________________________________<br>
Coin-discuss mailing list<br>
Coin-discuss@list.coin-or.org<br>
http://list.coin-or.org/mailman/listinfo/coin-discuss<br>
</tt></font>
<br>