That wikipedia ROCKS!
Seems like the most plausible way to get that kind of
coverage is through Test Driven Design, and I mean
the kind where you sorta define the thing you're trying
to build in the empty space of the tests, or whatever.
Automated might get buffer-overflow type stuff, but I
On 8/21/07, Dinner [EMAIL PROTECTED] wrote:
That wikipedia ROCKS!
Don't believe everything you read on wikipedia - it's descriptions of
some design patterns are pitiful, for example.
Seems like the most plausible way to get that kind of
coverage is through Test Driven Design
The point of
On 8/22/07, Sean Corfield wrote:
On 8/21/07, Dinner [EMAIL PROTECTED] wrote:
That wikipedia ROCKS!
Don't believe everything you read on wikipedia - it's descriptions of
some design patterns are pitiful, for example.
Fo sho- Did you see the page on Dada Art? ;-)
Do you ever edit those
Dinner wrote:
On 8/22/07, Sean Corfield wrote:
The point of code coverage is *measurability*. By definition, you get
better coverage by having better tests but that's irrelevant to the
process of figuring out the *amount* of coverage.
I could see how one could say I tested for X but it's
On 8/20/07, Rich wrote:
Is anyone aware of a code coverage tool for CF unit tests? If not, how
are
the rest of you handling unit test coverage (if at all)?
The CFUnit view in CFEclipse is cool, and there's also the TPTP
JUnit auto-generated stuff, but honestly, selenium has been the
most
What do you mean by code coverage?
Per the wonders of wikipedia:
Code coverage is a measure used in software testing. It describes the
degree to which the source code of a program has been tested.
I have just joined a new team, and we have quite a bit of legacy code for
older products and we
@dinner: code coverage determines the percentage of your code that is
actually being unit tested. For example, you could have a function in a
component that has a test case written for it, but the function could
contain if/elself/else statements, switch statements or other conditional
logic that
On 8/20/07, Rich [EMAIL PROTECTED] wrote:
Is anyone aware of a code coverage tool for CF unit tests? If not, how are
the rest of you handling unit test coverage (if at all)?
I get this question a lot since I'm doing a lot of automation/testing
consulting in the CF world and the answer is no.
It looks as though I am going to have to develop a solution for our needs,
but I will see if my company will allow me to release our efforts into the
public domain.
~|
ColdFusion 8 - Build next generation apps
today, with easy
of whether
this is a serious possibility for them. Maybe if there's enough demand it'd
move up the priority list?
Jaime Metcher
-Original Message-
From: Rich [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 22 August 2007 12:32 AM
To: CF-Talk
Subject: RE: Unit Testing Code Coverage
10 matches
Mail list logo
