Mail Archives: cygwin-developers/2001/10/02/07:53:41

Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <002901c14b39$179d7a20$01000001@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "egor duda" <cygwin-developers AT cygwin DOT com>
References: <20011001194848 DOT A30610 AT redhat DOT com> <1399887427 DOT 20011002153216 AT logos-m DOT ru>
Subject: Re: The test suite is cool
Date: Tue, 2 Oct 2001 21:55:06 +1000
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

----- Original Message -----
From: "egor duda" <deo AT logos-m DOT ru>

> what i definitely _can_ write is a testsuite TODO :) i have some ideas
> to make testsuite more useful (this includes [better] w9x support,
> testing for memory leaks, some kind of benchmarking etc.)

Can you give me some insight into how you see the daemon (assuming there
will be one at some point) being tested within the suite framework? I.e.
does the daemon get started via servicemanager/via make check
command/how does setting the correct daemon use get done?

This isn't an issue today, but...


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019