Testing tip: Write your test modules like so for a smaller release binary

I wish there were 2 more annotations: :testing, :no_testing (or something similar), with the following meaning:
When a regular (no test) build compiles then :testing excludeAnnotation is set, when a test build is compiling then :no_testing excludeAnnotation is set. This would enable us to write code like:

// 1st example to exclude prod code from test:
(:no_testing)
function myInit() {
    // do the regular init (like views, etc)
}
(:testing)
function myInit() {
    // do nothing
}

// 2nd example to exclude test-only code from release:
(:testing)
function commonTest(str as String) as Boolean {
    // this function is only needed for tests
    return str.length() < 5;
}
(:test)
function myTest1() {
    commonTest("foo");
}
(:test)
function myTest2() {
    commonTest("bar");
}

I think it's easy to get messy when you mix in your test functions within the same file as your regular code.

A seperate module for your tests as waterkip did it is acceptable, but personally I'm still a fan of the seperate test project approach I wrote about aeon's ago https://starttorun.info/tutorial-how-to-create-connect-iq-unit-test-project/ 

Linking you now have to do through monkey.jungle but the basics of the concept (separating test code from actual code) stay the same.

Thanks. I've seen it in the past, but it was too early in my Monkey C carrier. I refactored my code now

I was trying to read your tutorial but got the message that there a "critical error on the website". I know I've read it before but just like flocsy, it was too early in my Monkey C career. Would love to read again.

I disabled the wordpress code plugin, so no more syntax highlighting, but it fixed the critical error issue.

Strange, I cant view the post. Tried Chrome, Edge and Firefox.

I've cleared the cached pages server side now, try again :)

Yes, now I can read it. Thank you!

Don't know if you use VS Code nowadays (I do), but is the equivalent of eclipse's linking of folder to use what VC Code calls "multi-root workspaces"?