<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><div class="">Standard practice is to create a hidden test module. <a href="https://www.drupal.org/node/302577">https://www.drupal.org/node/302577</a></div><br class=""><div><div class="">On Dec 1, 2014, at 2:19 PM, Jeff Greenberg wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="border-collapse: separate; font-family: Helvetica; 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; " class="Apple-style-span">In Drupal 7, I have a requirement to simpletest a functional group of methods... one test comprised of about 1800 subtest permutations. <div class=""><br class=""></div><div class="">The issue I have is that these are back-end functions with no UI interaction, yet simpletest unit test, from what I read, does not provide the functionality for accessing the db, creating test tables and data, etc.</div><div class=""><br class=""></div><div class="">Do I fudge it by having a menu callback, or by having an admin page with a button if necessary, so that I can webtest, or do I manually include db.inc, etc. so that I can access the db, (though I think it would need to be much dirtier than that)?</div></span></blockquote></div><br class=""></body></html>