[http-state] Call for participation: Test harness
Adam Barth <ietf@adambarth.com> Wed, 05 August 2009 16:20 UTC
Return-Path: <adam@adambarth.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 773EF3A718B for <http-state@core3.amsl.com>; Wed, 5 Aug 2009 09:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L56n83dvpcIB for <http-state@core3.amsl.com>; Wed, 5 Aug 2009 09:20:49 -0700 (PDT)
Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.211.174]) by core3.amsl.com (Postfix) with ESMTP id A4B533A6A2E for <http-state@ietf.org>; Wed, 5 Aug 2009 09:20:49 -0700 (PDT)
Received: by ywh4 with SMTP id 4so339566ywh.17 for <http-state@ietf.org>; Wed, 05 Aug 2009 09:20:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.11.18 with SMTP id 18mr14925585ybk.173.1249489250186; Wed, 05 Aug 2009 09:20:50 -0700 (PDT)
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 05 Aug 2009 09:20:30 -0700
Message-ID: <7789133a0908050920x2d135160wa713c3497166e922@mail.gmail.com>
To: http-state <http-state@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [http-state] Call for participation: Test harness
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2009 16:20:50 -0000
As we revise the draft to more closely match reality, I'd like to add a test for each functional change we make, much like adding regression tests in a software engineering project. To do this, we need a testing harness that makes adding new tests easy. If you, or someone you know, is so inclined, I would welcome a patch that adds a testing harness to the repository. What might make sense is a simple Python web server (a la http://fragments.turtlemeat.com/pythonwebserver.php) that reads in tests from individual files. We could then point a user agent at the server and see whether it passes or fails the tests. Ideally, the workflow for adding a new test would be as simple as adding a file with the test case and the expected results. Now seems like an opportune time to create such as harness because that work can proceed in parallel with drafting a straw-man specification. Adam