You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use an env.sh based on template.env.sh and do not change the default users then running test/install_and_run_tests.sh produces an error while running this statement create or replace synonym ut3_user.coverage_helper for ut3_tester_helper.coverage_helper; because the user ut3_user does not exist.
Expected behavior
Installation of tests work when using the default usernames in template.env.sh.
Workaround
Configure export UT3_USER=UT3_USER in env.sh.
Off topic remark
I do not see a value in making the test users configurable. Quite the contrary. It makes the the test setup more complicated and also more fragile. Making the utPLSQL schema owner for production use configurable makes sense. But the testing users? - I don't think so.
The text was updated successfully, but these errors were encountered:
Hi @PhilippSalvisberg
I agree with you on that one.
There is no need to have those configurable and having them hard-coded would make things much clearer.
It would be definitely good to clean this up.
Describe the bug
In template.env.sh the user name
UT3$USER#
is configured for${UT3_USER}
. In install_ut3_tester_helper.sql the user is hard coded.ut3_user
is used.When I use an
env.sh
based ontemplate.env.sh
and do not change the default users then runningtest/install_and_run_tests.sh
produces an error while running this statementcreate or replace synonym ut3_user.coverage_helper for ut3_tester_helper.coverage_helper;
because the userut3_user
does not exist.Expected behavior
Installation of tests work when using the default usernames in
template.env.sh
.Workaround
Configure
export UT3_USER=UT3_USER
inenv.sh
.Off topic remark
I do not see a value in making the test users configurable. Quite the contrary. It makes the the test setup more complicated and also more fragile. Making the utPLSQL schema owner for production use configurable makes sense. But the testing users? - I don't think so.
The text was updated successfully, but these errors were encountered: