5 Replies Latest reply on Oct 16, 2014 7:34 PM by val.2046

Unit Testing: Is there a way to make the Dynamic Value Query to run after Startup processes?

val.2046 Sep 16, 2014 2:42 PM

I am wondering why the Dynamic Value Query is being run prior to the Startup processes? Logically it makes sense to run it after them.

For example, I am testing a stored proc that is supposed to delete a record and I would like to create that test record to be deleted as a part of the Startup processes prior to executing the stored proc call to delete such test record. Apparently the Dynamic Value Query does not return the test record as a parameter for calling the tested stored proc, which makes me think the query is run prior to the startup processes by design...

Please advise...

Thanks,

Val

1. Re: Unit Testing: Is there a way to make the Dynamic Value Query to run after Startup processes?

val.2046 Sep 16, 2014 3:45 PM (in response to val.2046)

I am thinking about creating a special suite for the stored procs with deleting records and include it as a sub-suite into the the main suite of tests for the package as a workaround, but still would love to hear a confirmation from the dev team that I am not supposed to use the unit test's startup processes to create the test records to be deleted and to be accessed in the dynamic value query...

Please advise...

Thanks,

Val
Like Show 0 Likes(0)

Actions
2. Re: Unit Testing: Is there a way to make the Dynamic Value Query to run after Startup processes?

val.2046 Sep 30, 2014 7:04 PM (in response to val.2046)

Dear SQL Developer Team,

Any insight into why the Dynamic Value Query is still being run prior to the startup processes on the the unit test level? Isn't it logical to run it after the unit test startup processes?

I see my enhancement request for this is still sitting there in the Feature Requests queue with the Open status for more than four years, although a few more folks also voted for it with their 10s:

https://apex.oracle.com/pls/apex/f?p=43135:7:3192213900678::NO:RP,7:P7_ID:23761

Moving the startup processes to the Suite level is now available as a workaround, but I am curious if this design enhancement can be finally implemented... We would love to keep the startup and teardown processes on the unit test level, where they belong...

Please advise...

Thanks,

Val

P.S. A fellow PL/SQL Developer, if you are reading this and would like to vote for this fix/feature/enhancement, please go to the Feature Requests page on the Oracle SQL Developer Exchange (https://apex.oracle.com/pls/apex/f?p=43135:7:3192213900678::NO:RP,7:P7_ID:23761) and leave your vote there, so the enhancement could get some higher rating/attention and get implemented... Thanks!
Like Show 0 Likes(0)

Actions
3. Re: Unit Testing: Is there a way to make the Dynamic Value Query to run after Startup processes?

val.2046 Oct 13, 2014 4:13 PM (in response to val.2046)

Any update from the SQL Developer team on this?

Thanks,

Val
Like Show 0 Likes(0)

Actions
4. Re: Unit Testing: Is there a way to make the Dynamic Value Query to run after Startup processes?

val.2046 Oct 16, 2014 2:07 PM (in response to val.2046)

If the backward compatibility is of a concern, you can add a checkbox to the UI to change (when needed) the default order of the execution between the startup processes and the dynamic value query. To force the sturtup processes to run before the dynamic value query is executed...

Any thoughts from the SQL Developer team on this issue?

Thanks,

Val
Like Show 0 Likes(0)

Actions
5. Re: Unit Testing: Is there a way to make the Dynamic Value Query to run after Startup processes?

val.2046 Oct 16, 2014 7:34 PM (in response to val.2046)

As this thread does not see any traction/attention from the SQL Developer team for a while I had to submit a formal enhancement request on metalink:

ER: 19834977 - IN THE UNIT TEST REQUEST TO ALLOW CHANGING THE RUN ORDER OF THE START UP PROCESS

Thanks,

Val
Like Show 0 Likes(0)

Actions

Go to original post