Hi there, we use utplsql extensively here, so thank you for activating this project!
We are using version 2.3.0 and the order of tests run in a suite is not in alphabetical order.
I have an intermittent test failure and I am trying to determine if another test is the issue, but because each suite run results in a different test order this is difficult to do!
I did read that a bug ahd been fixed and released but downloading and comparing the code it looks like I have the latest version (exec dbms_output.put_line (utPLSQL.version)
2.3.0 ) but the test order is still not right. Is this still a known issue?
many thanks
magnus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, you're right, this should have been fixed since v2.2.2.
Are you able to document how to reproduce this?
It's worth noting as well that you can set the per_method_setup_in parameter of utplsql.test and utplsql.run to TRUE so the ut_setup and ut_teardown procedures run before and after each test - that way (assuming these are setting up your test data properly) you can keep the tests independent of each other.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I get some time I will put together a test to show this behaviour, unfortunately I don't have time right now :(
I believe we are setting up and tearing down between tests otherwise they wouldn't work so I am guessing the default behaviour for per_method_setup_in is set to true but I will give it a go and see if it turns out differently.
thanks
magnus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there, we use utplsql extensively here, so thank you for activating this project!
We are using version 2.3.0 and the order of tests run in a suite is not in alphabetical order.
I have an intermittent test failure and I am trying to determine if another test is the issue, but because each suite run results in a different test order this is difficult to do!
I did read that a bug ahd been fixed and released but downloading and comparing the code it looks like I have the latest version (exec dbms_output.put_line (utPLSQL.version)
2.3.0 ) but the test order is still not right. Is this still a known issue?
many thanks
magnus
Yes, you're right, this should have been fixed since v2.2.2.
Are you able to document how to reproduce this?
It's worth noting as well that you can set the
per_method_setup_inparameter ofutplsql.testandutplsql.runtoTRUEso theut_setupandut_teardownprocedures run before and after each test - that way (assuming these are setting up your test data properly) you can keep the tests independent of each other.Hi Paul, thanks for the response.
If I get some time I will put together a test to show this behaviour, unfortunately I don't have time right now :(
I believe we are setting up and tearing down between tests otherwise they wouldn't work so I am guessing the default behaviour for per_method_setup_in is set to true but I will give it a go and see if it turns out differently.
thanks
magnus