> I'd like to know how others approach testing. I work for a bank and
there are some fairly paranoid people here. My philosophy is to test
only the webforms that were changed. But people here are telling me the
whole app needs to be tested. I think that's crazy. What's your
opinion?
It depends on how your software is structured I would say.
If you are changing business functions in a independend layer as
CreatePayment(x,x,x) then a test of the whole system could be justified. If
your only are changing presentation / or the use of such a business layer I
would say it would be overreacting.
But then again. Your statements somehow does not make sence.
If it is a bank and quality attributes such as security and safty is primary
concerns then:
1. There should be procedures to follow regarding your issue that would
overull any single developer concern.
2. If the system is a "critical" system there should be some automated test
and job of testing the would be "easy".
Are you developing a utility application to support som internal business?
If so, are you interfacing with som common business layers?
Anyway. It´s very hard to tell if you should test. If you KNOW there is no
side effects in the cahnge you made then there should be no problem (in a
non critical system). Again is it critical you would still want to test the
functionlaity. Eg. If you are recompiling youe application and a lot of
individual DLL are genereated and a corruption maybe of a bad disksector you
would still be in trouble.
Regards
Anders Kjellerup Jacobsen
Developer @ Cryos.dk