Comments on: Why you should never ever copy code – An example of complete chaos http://technology.amis.nl/2007/04/18/why-you-should-never-ever-copy-code-an-example-of-complete-chaos/?utm_source=rss&utm_medium=rss&utm_campaign=why-you-should-never-ever-copy-code-an-example-of-complete-chaos Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Ramin Orujov http://technology.amis.nl/2007/04/18/why-you-should-never-ever-copy-code-an-example-of-complete-chaos/#comment-4543 Ramin Orujov Wed, 17 Feb 2010 09:46:25 +0000 http://technology.amis.nl/blog/?p=1866#comment-4543 Hi, i work in telecom industry. We have a lot of legacy PL/SQL code. I have a package of 2500 lines of PL/SQL that at least 2-3 developers worked on it before me.
This package works on production server. Now I have to change it, add some new business logic and also refactor it in order to pass QA tests.
Without reliable unit testing, a lot of time and work it is very hard to refactor. Because it is related to billing system, changes are very risky.

I have created some plan for me:

1.Research of PL/SQL unit testing tools
2.Read “Oracle PLSQL Best Practices, 2nd edition by Steven Feuerstein
3.Read some books on refactoring (general concepts)
4.Research on PL/SQL refactoring
5.Develop unit tests for each procedure/function.

I can share these resources:

1. There are some PL/SQL unit testing tools
CodeTester
utPLSQL
Pluto
PLUnit
dbFit

I liked Quest Code Tester but it is not free (595$ per user), our company is going to buy it.
For open source solutions try
a. utPLSQL
b. Oracle SQL Developer – http://www.oracle.com/technology/obe/11gr2_db_prod/appdev/sqldev/sqldev_unit_test/sqldev_unit_test_otn.htm

2. http://www.amazon.com/Oracle-PL-SQL-Best-Practices/dp/0596514107
3. Practical Best PL/SQL Video Series produced by Steven Feuerstein
http://www.toadworld.com/EXPERTS/StevenFeuersteinsPLSQLObsession/PracticalBestPLSQLVideoSeries/tabid/154/Default.aspx

Best Regards,
Ramin Orujov.

]]> By: Jeroen van Wilgenburg http://technology.amis.nl/2007/04/18/why-you-should-never-ever-copy-code-an-example-of-complete-chaos/#comment-4542 Jeroen van Wilgenburg Sun, 29 Apr 2007 10:58:04 +0000 http://technology.amis.nl/blog/?p=1866#comment-4542 Someone else probably had the same experience I had: http://blog.james-carr.org/?p=66

]]> By: p3t0r http://technology.amis.nl/2007/04/18/why-you-should-never-ever-copy-code-an-example-of-complete-chaos/#comment-4541 p3t0r Wed, 18 Apr 2007 23:11:24 +0000 http://technology.amis.nl/blog/?p=1866#comment-4541 Wow… those numbers just don’t make any sense… How does anyone find his/her way in such a huge amount of templates (I guess strongly types Java would be more doable). By the way… wikipedia does actually contain some occasions in which it could be OK to break the DRY (don’t repeat yourself) principle (http://en.wikipedia.org/wiki/Don't_repeat_yourself)

]]> By: Patrick Wolf http://technology.amis.nl/2007/04/18/why-you-should-never-ever-copy-code-an-example-of-complete-chaos/#comment-4540 Patrick Wolf Wed, 18 Apr 2007 19:06:29 +0000 http://technology.amis.nl/blog/?p=1866#comment-4540 No comment :-)

]]>