Re: What are you doing with.NET and integrating into IBM i?

I think if your focus was on only a few products, like if you are a vendor.
Test units makes sense and you would probably have a QA dept that would
create those tests. For a "normal" business, while test units can be
useful, you waste so much dev time creating the tests when the company
wants to see the product created so you can move on to the next project. I
tried it, I finally stopped and deleted what I created. I spent days trying
to create tests and just gave up.

--
Mike Wills
http://mikewills.me


On Thu, Dec 20, 2012 at 10:17 PM, Walden H. Leverich <
WaldenL@xxxxxxxxxxxxxxx> wrote:

I've read the books and gone to the user groups, like I said, I really do
want to find a solution that works. But I've always found that in the end
you're either running a setup that creates a customer named "bob" and then
testing that the customer you just read is "bob" or you end up mocking out
so much that you're really testing your mocks and not your code. That's why
I asked about real-life beneficial unit tests. Not so you can check a box
that says you do unit tests, but rather something that you honestly think
will find bugs. And even then, how are you unit testing UI where the vast
majority of our bugs end up (browser/JavaScript issues)

-Walden