|
|
From cpoole@... Thu Jul 09 23:17:30 2009
Return-Path: <cpoole@...>
X-Sender: cpoole@...
X-Apparently-To: testdrivendevelopment@yahoogroups.com
X-Received: (qmail 86304 invoked from network); 10 Jul 2009 06:17:30 -0000
X-Received: from unknown (98.137.34.45)
by m4.grp.sp2.yahoo.com with QMQP; 10 Jul 2009 06:17:30 -0000
X-Received: from unknown (HELO mailout18.yourhostingaccount.com) (65.254.253.145)
by mta2.grp.sp2.yahoo.com with SMTP; 10 Jul 2009 06:17:30 -0000
X-Received: from mailscan21.yourhostingaccount.com ([10.1.15.21] helo=mailscan21.yourhostingaccount.com)
by mailout18.yourhostingaccount.com with esmtp (Exim)
id 1MP9PY-0004cD-4x
for testdrivendevelopment@yahoogroups.com; Fri, 10 Jul 2009 02:16:44 -0400
X-Received: from impout03.yourhostingaccount.com ([10.1.55.3] helo=impout03.yourhostingaccount.com)
by mailscan21.yourhostingaccount.com with esmtp (Exim)
id 1MP9PX-0000Oj-Ts
for testdrivendevelopment@yahoogroups.com; Fri, 10 Jul 2009 02:16:43 -0400
X-Received: from authsmtp05.yourhostingaccount.com ([10.1.18.5])
by impout03.yourhostingaccount.com with NO UCE
id E6Gj1c00206ZpSa0000000; Fri, 10 Jul 2009 02:16:43 -0400
X-EN-OrigOutIP: 10.1.18.5
X-EN-IMPSID: E6Gj1c00206ZpSa0000000
X-Received: from or-65-40-222-200.dyn.embarqhsd.net ([65.40.222.200] helo=ferrari)
by authsmtp05.yourhostingaccount.com with esmtpa (Exim)
id 1MP9PX-0002oP-EO
for testdrivendevelopment@yahoogroups.com; Fri, 10 Jul 2009 02:16:43 -0400
To: <testdrivendevelopment@yahoogroups.com>
Date: Thu, 9 Jul 2009 23:15:58 -0700
Message-ID: <000f01ca0125$e5c1edf0$6401a8c0@ferrari>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <64b8ffb10907092149g1d24de56j8954eba10d99d3cb@...>
Thread-Index: AcoBGgIhFK9VUQjZQZWJr2CmBdoBpwAC5TyQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-EN-UserInfo: 6922cf196b87f3584fc798087c9a72bd:3356ecf59c1dbdb5df18646fb601be29
X-EN-AuthUser: cpoole@...
X-EN-OrigIP: 65.40.222.200
X-EN-OrigHost: or-65-40-222-200.dyn.embarqhsd.net
X-Originating-IP: 65.254.253.145
X-eGroups-Msg-Info: 1:12:0:0:0
From: "Charlie Poole" <cpoole@...>
Subject: RE: [TDD] Agile response to combinatorial explosion
X-Yahoo-Group-Post: member; u=47198710; y=a0fazGrP6LLOP11CJbkA4dv9awdppsHLz7PMNZugIKuxWK1eyYk
X-Yahoo-Profile: cpoole98370
If you're working in the .NET world, either NUnit or MbUnit
have a Pairwise attribute used to generate test cases from
a set of parameter values.
Charlie
> -----Original Message-----
> From: testdrivendevelopment@yahoogroups.com
> [mailto:testdrivendevelopment@yahoogroups.com] On Behalf Of Dale Emery
> Sent: Thursday, July 09, 2009 9:50 PM
> To: testdrivendevelopment@yahoogroups.com
> Subject: Re: [TDD] Agile response to combinatorial explosion
>
> Hi Andrew,
>
> I'm trying to figure out the right approach in my thinking
> here. Suppose you
> > have an application which has 10 different configuration
> options. Each
> > option has 3 different settings. It doesn't take rocket science to
> > figure out that this means 3^10 or over 59000 configurations. And
> > those are small numbers! Certainly we can't write a test for every
> > single one of these cases. Yet it's also hard to be absolutely sure
> > that they're completely independent. I recently had a UI
> bug that was
> > unexpectedly caused by bad data in a completely different
> area of the
> > site, and I really don't think it was caused by poor
> design. So what
> > do we make of this? How shall we then test?
>
>
> One common approach is to make this simplifying assumption:
> Most combination-related problems are caused by interactions
> of PAIRs of variables, and very few are caused by larger tuples.
>
> I have no idea under what circumstances that assumption is
> warranted. I do know that making the assumption greatly
> reduces the number of combinations you need. There's a
> technique called All Pairs Analysis (aka Pairwise
> Analysis) that yields a minimal set of combinations that
> includes every pair of values for every pair of variables.
>
> If you're willing to make the pairwise assumption (and accept
> the attendant risks), give All Pairs Analysis a try. James
> Bach offers a free tool on his web site:
> http://www.satisfice.com/tools.shtml
>
> Dale
>
> --
> Dale Emery, Consultant
> Inspiring Leadership for Software People
> Web: http://dhemery.com
> Weblog: http://cwd.dhemery.com
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
|
"Charlie Poole" <cpoole@...>
cpoole98370
Offline Send Email
|
|