<HTML><BODY><p style="margin-top: 0px;" dir="ltr">Certain types of tests could produce a security risk if left as part of a production app. I think if they are global and the app allows user plugins.</p>
<div id="mail-app-auto-default-signature">
<p dir="ltr">--<br> Thanks<br> Brian</p>
</div>Wednesday, 24 June 2020, 02:16AM -07:00 from Christof Thalhofer <a href="mailto:chrisml@deganius.de">chrisml@deganius.de</a>:<br><br><blockquote id="mail-app-auto-quote" cite="15929901690000016387" style="border-left:1px solid #0878BD; margin:0px 0px 0px 10px; padding:0px 0px 0px 10px;">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div >
<base target="_self" href="https://e-aj.my.com/" />
<div id="style_15929901690000016387_BODY">Am 23.06.20 um 09:56 schrieb Benoît Minisini:<br>
<br>
>> If yes, consider opening a feature request. I vaguely remember everyone<br>
>> agreeing that tests should *not* be included in "production" things.<br>
> <br>
> Mmm... yes I didn't really think about that.<br>
> <br>
> At the moment, test modules are included in the executable as any other <br>
> classes.<br>
> <br>
> It allows to test the executable using the '-T' interpreter option.<br>
> <br>
> But on the other hand you are providing your tests to the final user in <br>
> an executable bigger thant it should be. Maybe not a wanted thing...<br>
<br>
I think the testclasses do no harm. In an average project they are<br>
small. And it they exist they provide the benefit to test the executable<br>
on a machine in production later.<br>
<br>
For me I see no reason to remove them by default.<br>
<br>
> I guess I should add one more option!<br>
<br>
Yes, sure, why not.<br>
<br>
Alles Gute<br>
<br>
Christof Thalhofer<br>
<br>
-- <br>
Dies ist keine Signatur<br>
<br>
</div>
<div><br>
----[ <a href="http://gambaswiki.org/wiki/doc/netiquette" target="_blank" >http://gambaswiki.org/wiki/doc/netiquette</a> ]----<br>
<br>
</div>
<base target="_self" href="https://e-aj.my.com/" />
</div>
</div>
</blockquote></BODY></HTML>