Yeah, so I can understand that for some projects, especially “throw away” projects (ones that really are thrown away and not the ones that we wish were) and ones with little logic, unit tests are a waste of time.

I’ve used FlexUnit for an AS project before, and it worked fine. There’s not much too FlexUnit, and it’s nice to have a hook into JUnit (see Peter Martin’s blog) that allows the tests to be run from the command-line.

Let’s remember that I’ve only run ONE unit test in my entire life (yesterday in fact), so I am NOT an expert on the subject at all. What I can say with confidence, though, is that in some of my Flash work, unit tests are a waste of time when the code changes so rapidly, and requirements are in mad flux. I fail to see how I could be not only re-writing code, but re-writing unit testing code at the same time… just seems like a ridiculous waste of time. I could be wrong since I have a long way to go.

For anything that actually has to be maintained, yeah, I’m starting to see it… problem? All the dang unit testing stuff out there is for frikin’ Flex! It seems pure AS3 doesn’t get enough love. Still checking out ASUnit, and looking for others if ya know ’em.

Our CTO and others in management have encouraged us to receive emails to see what Client Managers are dealing with as well as what the Project Managers see. It really makes you think about how you build software, and where you should focus your time.

For example, suddenly those personal debuggers I’ve built take on a new importance to allow me to quickly diagnose a problem without having to check out code and setup a project to compile. Additionally, you take a lot of it personally, at least I do, which makes you want to try harder.

If you build products, or have the opportunity to do so, I encourage you to get exposure to what both current and new customers are saying.

I love reading your blog, and I definitely don’t want to stay on the wrong foot, so if you ever want to talk about this or my suckaz ways, shoot me an email.