Extreme programming - module template

[DANIESC SCHUTTE]

I surely did ask :) - and your argument holds true.  My reasoning: Having the stories / metaphors and spikes in "code" presents other coders with "options" that were visited as well as the description of this specific story/sub-story.

I like the idea of refactoring all of the stuff into a library - I am just not clear on the how :) ?

Short description:

1. Translate ISO8583 Message
1.1   Xlate_postbridge_in
1.1.1      Xlate_0200_100_message
1.1.2      Xlate_0200_101_message


1.1.1 and 1.1.2 only does translations of SPECIFIC MESSAGE types - but the test check for invalid routing and other related stuff.  (Local Tests).

1.1 selects the translation to use (1.1.1 or 1.1.2) so it does local as well as integration (does it work with 1.1.1) 

1 does n scenario test (person X with card Y rocks up at ATM Z doing transaction A for value B with pin C where the pin is invalid :) ).

The idea being the following - I'm trying to figure how to put ALL these tests (and some of them can be really "silly") inside of a library application.   Since we are introducing various costing schedules / payment schemes etc and non ISO8583 transactions - the whole system needs to be "retested" whenever a new "variable" is introduced.

I'm just afraid from a practical perspective - if the tests are not appended to the bottom of the code - it's easy for coders to shortcut the process of not adding new tests. 

thanks for your input
Danie



>>> Luke Gorrie <luke@REDACTED> 05/02/03 05:37PM >>>
"DANIESC SCHUTTE" <DANIESC.SCHUTTE@REDACTED> writes:

It looks really bureaucratic to me, with all the boilerplate. (Sorry,
you asked! :-))

I also think that is a lot of real code to be including in a template
(e.g. module_test/1). I think you should Refactor as much as possible
into a library, so you can have it Once-And-Only-Once in the source
code and change it more easily. Templates are really copy-and-paste
programming.

You could also write the version/0 function as a library routine if
you like. It could call YourModule:module_info(attributes) to extract
the 'revision' attribute, and then parse that.

Cheers,
Luke


#####################################################################################
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy and copies.
#####################################################################################