PL/SQL Developer test menu option

[Paul Burgess]

Performing right click on procedure or function and the test option in the menu doesnt appear on some functions and procedures but not others WHY?

 

[Remo Laubacher]

because they are private..

 

[Paul Burgess]

This doesnt appear to be the case as the procedures/functions are showing up when a describe of the package thay are contained within is performed.

 

[Makker]

Did you recompile the package (with debug info)?
Since I allways compile with debug info (I allways want that, particularly in development/test db), I don't know exactly the behaviour when having no debug-info. It might be related to availability of debug-info?

 

[Marco Kalter]

You can always create and run a Test Script, regardless of the presence of debug information. Perhaps you can send me the package specification and the name of a function for which the test function does not appear?

 

[cmj]

I'm having the same problem. I'm running 7.0.2.1076. I'm not seeing the test option on the menu for programs in a package that I have often tested before. Under tools/preferences/debugger I have all the check boxes checked. I have recompiled both the package and the body. The programs I'm trying to test are not private.

I didn't think I'd changed any PL/SQL Developer settings. What could I be missing?

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the shortcut and add the debugsql parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debugsql

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.

 

[cmj]

Can I attach debug.txt or should I just copy it here? It is almost 8000 lines. I don't see a way to attach a file.

 

[cmj]

AH HA! I think I've got it, and the problem is the same one as another posting I began yesterday about getting the message "Compiled with errors" but list of errors when I compile my package.

Both packages are oldsters and have long lists of "rem" comments, their modification history, at their beginning. When I remove those commments both problems go away: I get a list of errors rather than the lonely little "compiled with errors" message, and when the package compiles without errors the Test option appears in the menu when I right-click a program in the package.

I had the exact same problem when I first began using PL/SQL Developer, although I don't remember the exact error I encountered. It was the reason I logged my very first question in this forum. I discovered at that time that there is some magic number of characters you can have in "rem" comments; after that errors arise. I solved the problem then by changing the comment prefix to "--", which worked just fine. The trouble is that the standard here is "rem" and I am the only developer using your product.

Since I am an old programmer, I have a tiney little retention span for problems like this. I am bound to encounter it again one day unless you can fix it, and I'll have to be back here asking the same old question.

I love this forum and I love PL/SQL Developer. Keep up the good work, fix this problem, and let's all get on with the job.

Thank you!