In the previous article, I've briefly demonstrated creation of a very simple unit test using a tool built-in to the SQL Developer. Let's see what issues you'll have to face when using this tool in a real-world project - not just traditional bugs (fixable) but consequences of decisions made when designing the system (thus inherent, not easily fixable, problems).
When writing PL/SQL procedure or function, you may want to create a unit test - something that tests the piece of code automatically. There are several projects intended for writing unit tests of a PL/SQL code, e.g. the well-established utPLSQL or a newer PLUTO, but since version 2.1 the SQL Developer contains it's own unit testing solution. As we have used it for several months on a real project, I'll take the liberty to present my experiences - maybe you're considering using it on a project too.
