× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The reason why we find them useful even though they are a pain to write is that we have such complicated business logic and a lot of really bizarre scenarios customers can get into that it was impossible to test them any other way.

So we mocked what a customer would look like in all the scenarios and made sure the calculations were correct.

When a new requirement came along and we needed to code it, we were ensured that all of our scenarios were still correct (regression testing).

I'm curious how other people are doing regression testing if not using unit tests.

-----Original Message-----
From: Mike Wills [mailto:mike@xxxxxxxxxxxx]
Sent: Friday, December 21, 2012 8:22 AM
To: .net use with the System i
Subject: Re: [SystemiDotNet] 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

--
This is the .net use with the System i (SystemiDotNet) mailing list To post a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/systemidotnet.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.