BillArms_GS wrote:If you changed the datatype and the application no longer works you will have to either change the datatype back or modify the unit tests. If changing the datatype was really a good idea and needed to happen you will have to modify the unit test scripts.
This is a questions about the capability / work around for SQL DEVELOPER unit testing. We are running Version 3.2.20.09.
We developeed a function with about 19 parameters. The parameter values are fetched from a table of test data by using a dynamic query. We had to change our parameters that had a datatype of DATE to a datatype of VARCHAR2. The unit tests which were 'written' against the old API now fail. What is the procedure to update the API for units tests? So far, all I can see doing is dropping the unit tests and 'rewriting' them by creating them against the new function call parameters. Is there an easier way?
BillArms_GS wrote:What are they written in? If they are PL/SQL procedures, functions, or packages you can use the code editor in SQL*Developer. If they are offline scirpts you can you any editor you want, like notepad.
Yes, I want to know how to modify the units test in SQL DEVELOPER.