cURL / Mailing Lists / curl-users / Single Mail

curl-users

RE: testing curl

From: David Byron <DByron_at_everdreamcorp.com>
Date: Sun, 22 Jun 2003 15:23:49 -0700

On Sun, 22 Jun 2003, Daniel Stenberg wrote:

> On Thu, 19 Jun 2003, David Byron wrote:
>
> > I'm using curl for a project that needs to run on multiple
> > target machines. For the rest of the project, I have dejagnu
> > set up to deal with getting files to remote machines,
> > executing them, parsing output, etc.
> >
> > I've run curl's tests locally and am just starting to dive
> > in to getting them to run remotely, but I thought I'd ping
> > the list to see if anyone else has done something similar,
> > or thought about it and decided not to, etc.
>
> I've never heard about anyone else doing work on this no, and
> I don't see the point in doing so. What's the benefit?

The benefit is that the build machine and the target machine get to be
different. That's big for cross compiling, but it also helps in my current
case where I need to run the same Windows binary on multiple flavors of
Windows, or even one that's not the same as my build machine.

> > The existence of sws, and proxies makes things a bit more
> > complicated. I'm just interested in running the client on
> > multiple targets, at least to start. Running sws and the
> > proxy on somewhere other than localhost will be useful
> > though.
>
> You mean on hosts where sws and the test scripts don't run
> but curl does?

I don't care as much where the servers run. If they run on the build
machine, that's fine. If the test framework can get curl on a different
target, it's probably easy to get the servers elsewhere as well, but it's
definitely secondary.

> Normally, if you just get curl to build, it'll work fine
> even if you can't make the test suite to run. The test suite
> is actually a lot less portable than curl itself.

All dejagnu needs to know about each target is how to copy files to it and
get a remote shell of some kind. The test suite itself doesn't know whether
its dealing with a remote or local target, so it doesn't have to be
portable.

> > Dejagnu could be taught to manage it all. Not sure how much
> > I'm signing up to do yet. What are the chances of patches
> > implementing dejagnu-based tests getting accepted?
>
> I know next to nothing about dejagnu so I wouldn't be able to
> answer this without you telling me a lot more about what
> impact/effect such a change would have on the test suite and
> my daily usage of it...

I think the best way is for me to show you. The public docs for dejagnu are
kind of a struggle to get through. I'm writing a program that ends up
spawning curl among other things. I'll try to get a test for that set up
with dejagnu. If you like it, great.

-DB

--
David Byron                   dbyron_at_everdream.com
Everdream                     http://www.everdream.com
6591 Dumbarton Circle         voice:(510)818-5550
Fremont, CA  94555            fax:(510)818-5510
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
Received on 2003-06-23