How do I design unit tests for multiple Perl modules in the same distribution? -
I am developing an internal framework that is created with a bunch of Pearl modules. All these modules are dependent on a single module which displays some Win32 functionality. For example, the modules A, B, C, D, etc. all depend on one module Z So import all these modules using "MyFormWork :: Z" All these modules A, B, C etc. can be used individually. No other frameworks are dependent on the module.
Now, with that simple design in mind - how can I design my unit tests. I am planning to use the test: more to test all the units. Should I write separate unit tests for each module? There are 25 different modules related to this profile any suggestions? Unit tests should cover Win32 functionality for
Z
. Unit tests for < A
should cover the functionality of A
which is not included in Z
. Repeat for C
, C
, D
, and so on.
If you think that C
, e
, and g
are doing the same thing and you have almost identical unit testing Writing, which is the signal for the reactor - extract common components (e.g., module CEG
) and bus C
, E , And examine the special parts of
G
to their original module.
Comments
Post a Comment