Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: "egor duda" 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 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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" > 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... Rob