Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 57458 invoked from network); 15 Sep 2004 00:07:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Sep 2004 00:07:22 -0000 Received: (qmail 72462 invoked by uid 500); 15 Sep 2004 00:07:21 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 72417 invoked by uid 500); 15 Sep 2004 00:07:21 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 72404 invoked by uid 99); 15 Sep 2004 00:07:21 -0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of aok123@bellsouth.net designates 205.152.59.69 as permitted sender) Received: from [205.152.59.69] (HELO imf21aec.mail.bellsouth.net) (205.152.59.69) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 14 Sep 2004 17:07:20 -0700 Received: from [172.16.1.8] ([65.80.200.112]) by imf21aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20040915000719.MLAD27018.imf21aec.mail.bellsouth.net@[172.16.1.8]> for ; Tue, 14 Sep 2004 20:07:19 -0400 Subject: [seda] An integration test harness From: Alex Karasulu To: directory Content-Type: text/plain Message-Id: <1095207025.1126.8.camel@fermi.trunk.joshua-tree.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 14 Sep 2004 20:10:25 -0400 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, After speaking to Trustin about our next steps with the SEDA framework for abstracting away transport details so UDP and TCP based services can live together we realized that a tight little test harness is required to end to end test this thing without the complexities of a microkernel. So this is a heads up to let you all know that I will be whipping something up together to fire up all these POJO services hardwired without any microkernel at all. The integration test harness will be used to makes sure all these peices work together. Now besides the test harness we're going to need a dummy protocol. I think I can just make one up for testing purposes. It will also make for an excellent tutorial. As Trustin and I refactor this code base we can make sure these beta tests and other unit tests still hold. Also getting 100% unit test coverage here is very important to me. If we can do this and handle the abstraction we're doing very well. Cheers, Alex