Where should the utPLSQL logic be stored? #27
Replies: 2 comments
|
Hi @HermanMol At the time when we were creating utPLSQL (10 years ago), it seemed reasonable to have external tools to deal with the topic of test package generation as it is outside of scope of the core framework but more a function on top of the framework. I agree that now it could be beneficial to have it as a library in utPLSQL itself and that it could allow for more reuse. It could fit nicely into additional tooling round the core framework itself. On a flip side, I do realise thought that modern AI models are very capable when it comes to test code generation. There is some room for brainstorming of ideas and visions for features as we go into 2027. Regards |
|
Hi @jgebal , |
Uh oh!
There was an error while loading. Please reload this page.
Problem or motivation
I was using the function in SQL Developer to
Generate utPLSQL testfrom the r-click popup menu in the object browser of SQL Develop. It works fine, but gives a rather poor output. My package to be tested contains a number of overloaded functions/procedures and in the generated ut package I cannot see which one is where. I then searched where the logic for this generation-function is located, but I could not find it in the database UT3 schema. (If appears to be in the Java sources, like UtplsqlDao.java.)Would it not be better to have a thin (Java) client and put the non-UI logic in the database? Then it is available for any client. (and can be tested using ... utPLSQL ;-)
Proposed solution
Put as much as possible utPLSQL logic in the database. Using database views and/or pipelined functions to collect the appropriate data and the UI only query those views/functions.
Alternatives considered
No response
Primary component affected
Multiple components
All reactions