Suggestion for Test Window

[ScottMattes]

I tried out the Execute SQL in a debug session yesterday while stepping through the code. Today I just ran the test without stepping through and after it finished I thought how nice it would be if I could do a SQL now that the test had run, but before clicking the Commit/Rollback.

p.s. Yes, I know I could run the test in debug and just step over the call to the code and then do the SQL, but if it is technically feasible to let us do SQL after the test runs and before we commit without having to do extra steps wouldn't that be nice.

p.s.s. well, I couldn't just step over the call to the code in the test window - I had to step into the package code, then find and place a breakpoint on the last line of the package code, then I could do the SQL.

p.s.s.s well, that bites, I added a SELECT to get the current SCN at the top of my Test Window, but when execution starts the Test Window Variables are no longer visible. So I ended up doing dbms_output.put_line since that output is no visible during the Test execution (which I think is a nice enhancement).

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[Hilarion]

Not sure if you know that you can turn off "AutoCommit after Execute" option for test windows (Tools / Preferences / Window Types / Test Window) and then you can execute anything in test windows and it will not commit, so you can swap your test code with any select statement to check the test results and do a commit or rollback.

 

[ScottMattes]

Marco, thank you.

Hilarion, I do always set autocommit off upon installing PLSD, and I know that I have to click the commit button to save my changes, BUT what you suggested hadn't dawned on me - thank you for the suggestion. A nice enough work-around (another job for clipjump!), but it would still be nice to have something like a SQL Window available from the Test Window.