[squid-dev] How to run the unit tests of Squid?

Tianyin Xu tixu at cs.ucsd.edu
Tue Oct 14 07:40:41 UTC 2014

Thanks, Amos!

One more question. I see test-builds.sh tries to run the tests in the
"test-suites" at the top directory. What's the difference between the test
under "src/tests" and "test-suites"?

I'm a little bit confused since you said the tests in "src/tests" contains
all the unit tests.

Also, I can successfully ran make check. But when I checked out the trunk
and ran ./test-builds.sh at the top directory, many tests fail. Is this
normal? (sorry I actually do not understand what "test-suites" does)

Oh, I forget to mention the web page I referred to. Actually I'm referring
to the "tasks needing a volunteer" in the following wiki page,
Are these tasks still alive? Since I'm looking at the tests, I think I can
give a hand.


On Mon, Oct 13, 2014 at 8:54 PM, Amos Jeffries <squid3 at treenet.co.nz> wrote:

> Hash: SHA1
> On 14/10/2014 2:39 p.m., Tianyin Xu wrote:
> > Hi all,
> >
> > Could anyone point me how to run the unit tests of Squid?
> >
> > I think the "src/tests" contains all the unit tests available, am I
> > right?
> >
> Yes, that contains all the unit-tests. A standard autotools "make
> check" runs those for any copy of the code.
> If you are building from a repository checkout you will also have the
> test-builds.sh script at the top directory. Running that will execute
> a longer set of tests with several permutations of ./configure options.
> NP: the full test suite can take 1-6hrs depending on your CPU speed.
> > But I failed to find information related to how to conduct these
> > tests.
> >
> > Also, I see a couple of "tasks needing a volunteer." Does it still
> > need to be done or it's obsolete?
> If you are referring to http://wiki.squid-cache.org/RoadMap/Tasks then
> yes, all those tasks still need to be completed.
> It is also just a small set of the items that we/I think need doing
> first to make the code generally easier to read and work with. If
> there is any other thing in particular you want to help get fixed up
> instead all ideas are welcome (there are ~400 open bugs for example).
> Thank you for your assistance with Squid.
> Amos
> Version: GnuPG v2.0.22 (MingW32)
> ndDbSCCwDTobY0h4IK5dpbfi9ZQZef5S+QN6+iB8OCNIe/VZ/p6pmW++EyYcFt3t
> sKHfVfsdx5H4Ecwo5Yh5ia1EW2LwfqxNesh+5KOuyTTFcLVEDYSsz8ZZTxbbVamy
> KOqvhJvH1zwcv/8DTRnbkyZyR1ixuA4/mNlcI8kDNB22E0G+6p6tmnGOIgW+32IJ
> Qv2CkCNOLW5895onlWFyDdKfRseKkWNxlrJxTFio32fFrafgoOLYWjKNz+cOssdX
> 9l/BWuqfjLdOne2idSzVADmL/Wf0JFhWqlPj5ZpUI8GLMYKGFabiqBdcOrLrSBk=
> =XCxo
> _______________________________________________
> squid-dev mailing list
> squid-dev at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-dev

Tianyin XU,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-dev/attachments/20141014/4d029ba0/attachment.html>

More information about the squid-dev mailing list