Hello, we are using Puppet 2.6 and need to support this version for some time. We wrote an installer in Puppet and it has rich codebase with pretty complex scenarios. The issue is we have missing dependencies there. Those are bugs we would like to catch, but they appear "randomly". Our testers or users hit those when running the installer in various conditions and environments (different memory, hdd speed, size etc). We have tested our manifests zillons of times and there are still some hidden dependency bugs we hit.
>From what I know, Puppet 2.6 executes steps from the same "level" in the tree "randomly". But it seems there is not a random() call, it just orders it depending on the environment. Is there any way (a hack or something) of shuffling the order so we would be able to stress test our Puppet codebase under all possible conditions? I would like to find a code which orders the steps and just shuffle it randomly, so we can test it 50 times to be sure no dependency bugs are there (from the statistical point of view)? Can you help me writing such a hack? Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/SjKsK2u1skYJ. 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.
