On Aug 9, 2009, at 4:36 PM, Markus wrote: > >> Right now integration tests are each in their own file >> corresponding to >> the source code file they covers. But in some cases like the one you >> present above, those integration tests covers large parts of the code >> (here the catalog, the transaction and the ral). So question is, in >> which test file would you put such test? > > I've had similar questions. In general, the integration tests > should be > structured around a systemic/functional taxonomy rather than per > implementation unit. Here they seem to be more "unit tests that are > allowed to leak a little," rather than aggressively crossing > implementation boundaries.
Definitely true. -- Learning is not attained by chance, it must be sought for with ardor and attended to with diligence. -- Abigail Adams --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
