|
Boost : |
From: Jeremy Siek (jsiek_at_[hidden])
Date: 2001-01-29 13:26:43
I have a concern about the requirement that the tests must execute
quickly.
For example, the current graph test only tests one version of the
adjacency_list class, but I was planning on adding code this week to make
sure all the versions of adjacency_list get tested in the regression test.
The problem is that there are 48 different versions of adjacency_list.
Also, when I finally get unit tests in place for all of the algorithms,
there will be another 40 or so tests.
Should the regressions test be divided into a "quick test" and
a "full test"?
Ciao,
Jeremy
On Mon, 29 Jan 2001, Beman Dawes wrote:
bdawes> There is a draft of a Boost Test Policy and Protocols page up at
bdawes> http://www.boost.org/more/test_policy.htm.
bdawes>
bdawes> (This page isn't "live" yet; there are no links to it from elsewhere on the
bdawes> site, and the links on the page won't all work.)
bdawes>
bdawes> It includes a bit of speculation - references to Boost test related
bdawes> libraries that haven't been accepted yet.
bdawes>
bdawes> Comments appreciated.
bdawes>
bdawes> --Beman
bdawes>
bdawes>
bdawes>
bdawes>
bdawes>
----------------------------------------------------------------------
Jeremy Siek www: http://www.lsc.nd.edu/~jsiek/
Ph.D. Candidate email: jsiek_at_[hidden]
Univ. of Notre Dame work phone: (219) 631-3906
----------------------------------------------------------------------
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk