Forum Discussion
Hi,
> we are also developers, we just don't write applications in the traditional sense.
With the only small difference (as for me) that usually we are working 'post-factum', running our tests for the already existing functionality and usually do not have much time to spend to adjust our test code to work for the tested version of the application.
Thus, while I am absolutely not against object oriented programming, but because of the above mentioned reasons, personally I value code clarity, simplicity and how easy is to modify the already existing code, I value these things higher than nice polished duplication-free design.
The best approach, is, as usual, somewhere in the middle :)
Yeah, ultimately whatever works for you and your team is the best approach. That said, I feel some object oriented automation scripts provide better clarity in the code just by not having duplicated code. You know that if you need to change the way something is done in your tests there is only one spot to do the update and everything works again. I would hate to have to track down X number of use cases to make a simple change. To me that's not an easy way to modify code. Just my opinion, again if you're approach works, then it's a good approach :)