Debug information for test scripts

[Worker]

Currently when I open a new test window and write some code in there, I am unable to set breakpoints in that code. Also when running the test script in the debugger, trying to view variable information gives "no debug information".

I don't know if it's even technically possible to do these things, but if it is, it seems like a useful enhancement.

 

[Marco Kalter]

You can only set breakpoints and view/set variables in stored program units, compiled in the database. In the anonymous PL/SQL Block of the Test Script, these things are unfortunately not possible. You can create a simple "debug" stored procedure that can act as a placeholder for the anonymous PL/SQL that you want to debug, and create a standard test script to run it. This way you can make the process a little bit more efficient.

 

[amaury]

Couldn't PLSQLdev do that for us? Create a stored procedure with a random name and run it.
The implementaion would not be so different from the "safe compilation" option.

Amaury

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[Christo Kutrovsky]

Setting break points in test window (anonymous block) is impossible due to Oracle limitations.

What about seeing variables (in anonymous blocks), is that an Oracle limitation too?

 

[Marco Kalter]

Yes, it's actually the same limitation.

 

[ScottMattes]

How about PLSD making it a non-anonymous block for us? Break points in the Test Window would be so handy!

 

[Marco Kalter]

See reply 3 & 4