[Tools-discuss] Testing and the SprintCoderSetup wiki page

Tom Pusateri <pusateri@bangj.com> Tue, 31 March 2020 14:26 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 755453A21EB for <tools-discuss@ietfa.amsl.com>; Tue, 31 Mar 2020 07:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bangj.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id V2KqwiC8jXDQ for <tools-discuss@ietfa.amsl.com>; Tue, 31 Mar 2020 07:26:49 -0700 (PDT)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6BB63A21EC for <tools-discuss@ietf.org>; Tue, 31 Mar 2020 07:26:49 -0700 (PDT)
Received: from [] (mta-107-13-246-59.nc.rr.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 9796B3B464 for <tools-discuss@ietf.org>; Tue, 31 Mar 2020 10:26:48 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bangj.com; s=201907; t=1585664808; bh=DRmmit1CpMHGg4/C45a64JAkqTD9ODvyMC90L7CjJTw=; h=From:Subject:Date:To:From; b=F1NcdHlfNeMrXC7EQPu1r5nnOsIY1DbX4o0GypUwqTlB3FvaYN5hiwxbHvUhzak37 9pTA1we6EuZZc/AUoU5Zr1s9f+L7Q4hxhalFRXdHQmGi9uxxK1BClubddF3+ddXpqi 9cv+n+cRytJhbpORXPzA862+UooiBFuWBKzO/42P1yyHIdEqgr8hDj59IJA5TrHq83 L7dyMNNQmI+47IP8+BNeWw9yrJVG04qNh7x8Xg1sgkSLJxb1oMmWp77AphZi2PWhwA 9Cs1XpKLYgKmdUEKAuHRe6YMMGxr3Vp8WO8VZjbPOOgUOGWaWRLBeVRs+u4S8Ubf7Z pMxJhChLHDR+w==
From: Tom Pusateri <pusateri@bangj.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
Message-Id: <572D6563-72CE-4D4F-A01C-6FF851E7A3C8@bangj.com>
Date: Tue, 31 Mar 2020 10:26:47 -0400
To: Tools Team Discussion <tools-discuss@ietf.org>
X-Mailer: Apple Mail (2.3608.
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/5WV0mDLvrjZcQQYe5FAkhWukV1o>
Subject: [Tools-discuss] Testing and the SprintCoderSetup wiki page
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 14:26:52 -0000

Thanks for the easy instructions on setting up a development environment. It’s been two sprints ago that I worked on anything in the datatracker and this made it easy.

I recently updated the SprintCoderSetup wiki page:


adding an example test invocation to only run a single test. This is helpful when you’re developing and don’t want to run the whole test suite each time.

But this made me wonder if it was possible to run against the existing full database and not a special test database? I know it’s unpredictable what is in the full database and that’s why a test database is useful but testing against real data is also useful.

On an unrelated note, when following these directions, I skipped the section “RUN THE TESTS” at first (shame) and went straight to “Start the Development Server”. This wasted a lot of time because the server wouldn’t start due to missing python modules. Going back and running the tests fixed this problem. While I shouldn’t have skipped the initial running of the tests, this shouldn’t have prevented the development server from running. Should I open a ticket on this?