I received this question from a user:
I’m basically looking for the best way to setup and use the tool in a sharedenvironment. I want every ID in the instance to see all the test casesand I want to be able to do that without having to switch to the schema thatthe test was originally built in. I need a single source for the truthfor each instance and I have not figured out a way to do that without doingexports and imports.
And I answered as follows:
There is no “automatic” way that Code Tester can do this for you.Access to test definitions and the programs they test are largely determined bythe underlying authority of the connected schema to run those programs.
You should first install Code Tester with public synonyms. This allows you toshare a common test repository with all schemas in your instance. I assume youhave done this.
Now I connect as schema A in Code Tester. I can only see test definitions thatI or others have created for programs that I own or I can execute.
If someone else created the test definition, then I can only run that test (aPL/SQL test package) if I have been granted execute authority on that package.We currently do not provide a way to do this from within Code Tester. You haveto run the grant yourself.
But…assuming that you grant execute authority on all application code to allschemas, then everyone SHOULD be able to build test definitions for any programand if you additionally grant execute on the generated test packages, theyshould be able to also run those packages.
I will provide one final caveat: I assume you are running 1.6. We are in finaltesting on our 1.8 release (due out in Feb) that will fix some bugs in theDashboard regarding display of test definitions that are owned by otherschemas. So if the above steps are acceptable to you and you run intovisibility issues, you might want to download the latest beta and try that.