Path: news.f.de.plusline.net!news-fra1.dfn.de!newsfeed.hanau.net!news.tiscali.de!tiscali!newsfeed1.ip.tiscali.net!proxad.net!216.239.36.134.MISMATCH!postnews.google.com!a75g2000cwd.googlegroups.com!not-for-mail
From: "EscVector" <Junk@webthere.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Oracle Unit Testing
Date: 2 Feb 2007 07:08:39 -0800
Organization: http://groups.google.com
Lines: 18
Message-ID: <1170428919.394921.293840@a75g2000cwd.googlegroups.com>
References: <1165935254.832348.74350@f1g2000cwa.googlegroups.com>
   <1165935372.231054.171760@80g2000cwy.googlegroups.com>
   <CtidnWGD0rccTePYnZ2dnUVZ_v-tnZ2d@comcast.com>
   <1165946106.430301.200370@l12g2000cwl.googlegroups.com>
   <457F6A93.6070700@comcast.net>
   <1170259065.894400.63160@h3g2000cwc.googlegroups.com>
   <1170278709.552105.115280@s48g2000cws.googlegroups.com>
   <1170288295.71113@bubbleator.drizzle.com>
   <1170406624.996767.94400@a75g2000cwd.googlegroups.com>
NNTP-Posting-Host: 72.165.244.50
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1170428925 6709 127.0.0.1 (2 Feb 2007 15:08:45 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 2 Feb 2007 15:08:45 +0000 (UTC)
In-Reply-To: <1170406624.996767.94400@a75g2000cwd.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: a75g2000cwd.googlegroups.com; posting-host=72.165.244.50;
   posting-account=YZW96w0AAABjQaJtmc4mPml4qWWrMr8V
Xref: news.f.de.plusline.net comp.databases.oracle.server:193499

On Feb 2, 3:57 am, "WebCom Systems" <i...@webcomsystems.co.uk> wrote:
> Actually I think this is getting off topic a bit.
>
> The point of the the Oracle Unit Testing web site is Unit Testing Best
> Practices.
> ie self testing code.
>
> I'd invite comments on that too.

Unit tests are great, but is objectification within the database the
way to go?  What is the fastest, most scalable approach?  I don't see
instrumentation any mention of response time here.  Business logic
that does what it is supposed to do is one thing, but what about
performance logic?  I like the approach on the surface, but I would
add performance instrumentation to the unit tests in the form of begin/
end trace and performance metrics within each distinct business
function.