René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cannot install tests when using default user names as provided in template.env.sh","articleBody":"## Describe the bug\r\n\r\nIn [template.env.sh](https://github.com/utPLSQL/utPLSQL/blob/85fd36d222680ebe1420d0fe40ed34520595a0b2/development/template.env.sh#L20) the user name `UT3$USER#` is configured for `${UT3_USER}`. In [install_ut3_tester_helper.sql](https://github.com/utPLSQL/utPLSQL/blob/85fd36d222680ebe1420d0fe40ed34520595a0b2/test/install_ut3_tester_helper.sql#L38) the user is hard coded. `ut3_user` is used.\r\n\r\nWhen 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.\r\n\r\n## Expected behavior\r\n\r\nInstallation of tests work when using the default usernames in `template.env.sh`. \r\n\r\n## Workaround\r\n\r\nConfigure `export UT3_USER=UT3_USER` in `env.sh`.\r\n\r\n## Off topic remark\r\n\r\nI 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.","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2022-03-13T15:21:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/1200/utPLSQL/issues/1200"}