On 09/26/2009 10:04 AM, Simon Riggs wrote:
>> If you think there's
>> something useful I could do, let me know and I'll take a look.
> I feel like I need a better way of unit testing new code. Some of the
> code in the patch is to handle corner cases, so recreating them is
> fairly hard. It is a nagging feeling that I am missing some knowledge
> here and would welcome some insight, or research, into better ways of
> doing general case unit testing.
You might try and steal ideas from EasyMock / PowerMock - but not sure
how well the ideas map to C.
Generally it means allowing the functions to be called from a "mock"
environment, where subroutine calls that might be called are stubbed out
to return sample data that would simulate your scenario. Object oriented
languages that require every object to provide an interface where most
object methods can be overridden are more ideal for performing this sort
I rarely ever see this sort of stuff in FOSS projects, and never that I
can remember in FOSS C projects. It's not easy, though.
I assume you are doing it through code changing right now. Commenting
out lines, replacing them with others, etc?
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2009-09-26 15:43:46|
|Subject: Re: WIP - syslogger infrastructure changes |
|Previous:||From: Simon Riggs||Date: 2009-09-26 14:04:37|
|Subject: Re: Hot Standby on git|