I am just starting to play with the code tester, hoping to include it in my regular development process. Here is the first snag I ran into.
The database security at my company follows the following model in development.
All developers log in to the database as themselves.
All developers writing pl/sql have permissions to compile code into any schema.
Passwords for application users are not published to the developers.
I created my first test for a package in schema x, and because I do not have execute granted on that package to my user directly, the test case would not compile in my schema.
I then change the owner of the test package in the edit test screen, and the test compiled successfully, but now I do not have permission to edit the test through the GUI, even though my user has permission to drop/modify the package in the database.
I am guessing that the security model for editing the tests is a simple, only the user owning the test case may edit it.
Is there a way around this?