<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 26, 2011, at 7:37 AM, Laurens Van Houtven wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Are there any better ways to pass test data to trial?<br></span></blockquote></div><br><div>Environment variables.</div><div><br></div><div>This isn't a <i>great</i> option, but I'd say it's definitely a better one than modules which monkeypatch stuff.</div><div><br></div><div>You can also have your test cases synthesize stuff out of data files or config files in your environment.</div><div><br></div><div>I'm not really inclined to make this super easy, since tests should by definition not be terribly configurable: the more knobs like this you have to turn, the less meaningful your test suite is likely to be.</div><div><br></div><div>So, today, I'd write something like this:</div><div><br></div><div>TXIEVERY_USERNAME=foo TXIEVERY_PW=bar TXIEVERY_CERT=baz.pem trial txievery</div><div><br></div><div>but if someone has a better thought, please chime in - this is by no means the last word on this. And I'm facing a similar issue soon so I'd love to hear some diversity of opinion here.</div><div><br></div><div>-glyph</div><div><br></div><div>PS: love the module name.</div><div><br></div></body></html>