Organizing your extensions
Starting with a new project, like we did with the LookupValue extension, I tend to have both the application and the test code in one VS Code folder just for one reason: practicality. This way, I only have to deploy one extension when verifying my work after an addition or change in either application or test code – or both, although TDD teaches us to do one or the other. This helps me to get my work done more efficiently.
Once the code is ready, however, we need to make sure that the application and test code end up in separate extensions – but still in the same repo – with the logical consequence that the test app will have a dependency on the application app. This way, we prevent tests from ending up, and possibly getting run, in a production environment. For this very reason, standard CRONUS does not contain the standard test codeunits – and test helper libraries.
Sure, if test codeunits are run within the test isolation...
