VBA-Unit-Tester VS VBA-Project-Information

VBA-Unit-Tester is a simple set of classes and interfaces to right and execute unit tests in VBA without Rubberduck. The basics are, each "Test Case" is an class, and a set of test which each share a common setup. A configuration class instructs a TestRunner on which TestCases and Tests to run. Another class logs the results and generates a few simple summary reports.

I just threw together a quick example of my testing system here: https://github.com/Beakerboy/VBA-Unit-Tester

I understand that VBA may be intended to help with spreadsheet handling at its birth(probably) but everything you mentioned is quite right because I am in the middle of developing a choropleth map in Excel using msoFreeForm shapes and another project which walks through VBA code modules to provide insight into VBProject with code obfuscation and visual codeflow diagrams, I got myself overwhelmed time and again and had to restart from scratch a number of times already. But with each iteration came, the need to compartmentalize/modularize, as I began to understand the need to improve my coding style or else.

You could write your own obfuscator code. I'm writing one.

Hi, sancarn, just greeting! We talked about your VBA shape Events class some time ago, I was working on a shape map project back then. I hope you will probably remember me once you see the image of the map. Still haven't finished it yet as I was side-tracked to another project which walks through VBA project code modules.