Testing and Source Distributions

[jgcode]

Hi

What is the standard practice for testing source distribution code:

Should I write tests cases for source code OR source distribution code OR both?

I can see issue with either choice:

Source only - you want to test source to pick up any errors before you make it into a source distribution but...

Distribution only - distribution may apply name changes and in case of an error with dependency code that meant the source was ok but the distribution isn't

Both - best coverage, but redundant tests case, changes mean updating code (tests) in two places (due to re-naming etc..)!

What do you guys do?

Cheers :beer:

JG

[Omar Mussa]

I added my response on the JKI Software Forums.

[Grampa_of_Oliva_n_Eden]

QUOTE (jgcode @ May 16 2009, 05:58 AM)

http://forums.jkisoft.com/index.php?showtopic=1104' rel='nofollow' target="_blank">[Cross posted to JKI]

Hi

What is the standard practice for testing source distribution code:

Should I write tests cases for source code OR source distribution code OR both?

I can see issue with either choice:

Source only - you want to test source to pick up any errors before you make it into a source distribution but...

Distribution only - distribution may apply name changes and in case of an error with dependency code that meant the source was ok but the distribution isn't

Both - best coverage, but redundant tests case, changes mean updating code (tests) in two places (due to re-naming etc..)!

What do you guys do?

Cheers :beer:

JG

Both.

The earlier in the development cycle a problem is found the easier it is to fix so unit testing at the very least.

But on the final application testing tells me if it works or not.

Ben