Whatever works for you. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Joseph L. Casale Sent: Thursday, April 24, 2014 3:14 PM To: '[email protected]' Subject: RE: [NTSysADM] RE: PowerShell unit testing
> +1 for modular [script] programming. > Build in terms of modules and standardize your variables. In the future you > can drop-in added functionality easy-peasy-lemon-squeezy. Like I said earlier, for one pager's or banging out simple scripts its not worth the time. But it doesn't scale. How do you know a change over there doesn't affect something over here? > I've read the Wikipedia article for TDD, and it sounds like throwing stuff at > a wall to see what sticks. Well, if you have not been around software development or written anything very large I can see how you might find that concept daunting. It is however a discipline but once learnt you'll never go back. For older more mature languages like Python, Java etc where good frameworks exist, it is pretty easy to setup a simple test. Some IDEs will even create an initial scaffold for testing and support easy integration of it. I use PyCharm for Python development and while I am writing I can run a test and maintain that changes I am making are actually correct. So it ends up being seamless and more often saves time... Give it a whirl next project. jlc
