Defensive programming tools would be a welcome addition. As Isaac said, this will become easier once NetLogo implements modules support.
I created several defensive programming functions/procedures in LogoUtils to help with this, based on the checkmate R package conventions:
For other discussions and solutions around code testing tools, see: