Cookie classes have got virtually 100% test coverage. Clover is horrible
way to spend a weekend [sigh]
Oleg
On Sat, 2004-04-24 at 18:51, Oleg Kalnichevski wrote:
Folks,
I think it is time we started using Clover reports for the CVS HEAD
development. Currently our test coverage is appalling
Nice work Oleg. Though not terribly glamorous, test work is definitely
needed.
Mike
On Apr 25, 2004, at 8:28 AM, Oleg Kalnichevski wrote:
Cookie classes have got virtually 100% test coverage. Clover is
horrible
way to spend a weekend [sigh]
Oleg
On Sat, 2004-04-24 at 18:51, Oleg
Folks,
I think it is time we started using Clover reports for the CVS HEAD
development. Currently our test coverage is appalling (meager 50%).
Since we have got a very flexible testing framework based on
SimpleHttpServer, we no longer have an excuse that certain complex
things cannot be adequately
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 24, 2004 12:52 PM
To: Jakarta Commons HttpClient mailing list
Subject: Test coverage
Folks,
I think it is time we started using Clover reports for the CVS HEAD
development. Currently our test coverage
Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 24, 2004 12:52 PM
To: Jakarta Commons HttpClient mailing list
Subject: Test coverage
Folks,
I think it is time we started using Clover reports for the CVS HEAD
development. Currently our test coverage is appalling (meager 50
, to the extent that
doing so does effectively enlarge the contract of the API. On the other
hand, where such tests already exists, I don't see much point in
removing them until they are actually in the way, either wrong or
testing deprecated functionality.
Personally, I'm hoping to achieve 100% test
comment over anything that I think may require a change to the code but
isn't clearly a bug.
I figure from time to time I can provide a list of issues that need to
be considered as I work my way through the codebase.
Personally, I'm hoping to achieve 100% test coverage firstly because
I've
to time I can provide a list of issues that need to
be considered as I work my way through the codebase.
Personally, I'm hoping to achieve 100% test coverage firstly because
I've discovered how dependent I am on having good test cases while
working on HttpClient (most people don't have
Again, if the contract of that method says that a leading white space
-- or some other irregularity -- causes a specific exception to be
thrown, it is good that there are test cases to verify the contract.
Maybe it is not the test that you dislike, but rather the behaviour of
the method? In
