ScottMattes
Member³
I would like the Test Window to include
:result := 'Running...'
right after the begin line.
:result := 'Running...'
right after the begin line.
Enhancement Request: Test Windows
- Thread starter ScottMattes
- Start date
You can modify the Test Window template to include this. The templateis only used when selecting File > New > Test Window from the main menu though, not when clicking the "Test" option for a function or procedure.
ScottMattes
Member³
I *almost always* use the right click Test option, so that is what I would like changed.
Hilarion
Member³
I'm not sure what's the goal of such change (see below). As I see this change as problematic for my use and no value added, I'd rather see it as an option and not a default one.
How would it work when I'd like to test a function?
The PL/SQL Developer uses "result" bind variable to receive the function value, which can cause the function return value indistinguishable from that hard-coded "Running..." text. This would also require changing the type of the "result" bind variable type from being specific to the function to a textual one.
How would it work when I'd like to test a function?
The PL/SQL Developer uses "result" bind variable to receive the function value, which can cause the function return value indistinguishable from that hard-coded "Running..." text. This would also require changing the type of the "result" bind variable type from being specific to the function to a textual one.
ScottMattes
Member³
Hilarion, I agree, and see that my request was incompatible with that variable.
I guess that what I want is an easy, visual clue that the Test has run (too much multi-tasking, just want to start a test, switch over to Word to read/write something and just glance back at the test window and see that it is done).
Maybe what I want is for the 'result' variable to be cleared when the execution of the test window starts (like a line ':result := null;'). i would hit start the Execute and see that the result variable was empty and when I glance back if it isn't empty I know the test has finished.
That, or a suit of armor like Tony Stark has.
I guess that what I want is an easy, visual clue that the Test has run (too much multi-tasking, just want to start a test, switch over to Word to read/write something and just glance back at the test window and see that it is done).
Maybe what I want is for the 'result' variable to be cleared when the execution of the test window starts (like a line ':result := null;'). i would hit start the Execute and see that the result variable was empty and when I glance back if it isn't empty I know the test has finished.
That, or a suit of armor like Tony Stark has.
Last edited:
Hilarion
Member³
I second the Tony Stark Iron Man suit. I'd even be satisfied by Mark II.
Going back to PL/SQL Developer, having some indicator of the test run being done could be nice, like the exact time it ended (beside the elapsed time).
Not sure if assigning NULL to the :result would work in some cases, as a tested function can return NULL as a valid result.
Having the "Notify end of long running queries" option working for the test window would also be nice. Not only when I use it to just execute code (not debug) but also when am waiting for the long running code to stop at a breakpoint.
Going back to PL/SQL Developer, having some indicator of the test run being done could be nice, like the exact time it ended (beside the elapsed time).
Not sure if assigning NULL to the :result would work in some cases, as a tested function can return NULL as a valid result.
Having the "Notify end of long running queries" option working for the test window would also be nice. Not only when I use it to just execute code (not debug) but also when am waiting for the long running code to stop at a breakpoint.
ScottMattes
Member³
How about
And when PLSD makes the Test Window it sets the variable type to Date in the grid below the code window (so that we see the Date & Time in the varialbe)
Code:
begin
:started := sysdate;
:ended := null;
-- call the function
:result := my_pkg.my_func;
:ended := sysdate;
end;And when PLSD makes the Test Window it sets the variable type to Date in the grid below the code window (so that we see the Date & Time in the varialbe)
Similar threads
- Discussion
