Deployed 45ad1dc with MkDocs version: 1.6.1

utPLSQL-SQLDeveloper.html

@@ -1636,43 +1636,43 @@ <h2 id="introduction">Introduction<a class="headerlink" href="#introduction" tit
 </ul>
 <h3 id="run-utplsql-test">Run utPLSQL test<a class="headerlink" href="#run-utplsql-test" title="Permanent link">&para;</a></h3>
 <p>In the Connections window, select a connection or one or more packages or package procedures to run utPLSQL tests. Or you can run utPLSQL tests directly from the PL/SQL editor. The test procedures are determined according to the cursor position in the PL/SQL editor.</p>
-<p><img alt="Run utPLSQL test" src="/images/run_utplsql_test.png" /></p>
+<p><img alt="Run utPLSQL test" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/run_utplsql_test.png" /></p>
 <h3 id="debug-utplsql-test">Debug utPLSQL test<a class="headerlink" href="#debug-utplsql-test" title="Permanent link">&para;</a></h3>
 <p>Select the tests to debug, the same way you would if you were just running them, but select <code>Debug utPLSQL test...</code> in the context menu.</p>
 <p>And then the PL/SQL Debugger is called for the generated, anonymous PL/SQL block.</p>
-<p><img alt="Anonymous PL/SQL block to debug utPLSQL test" src="/images/debug_utplsql_test_anonymous_block.png" /></p>
+<p><img alt="Anonymous PL/SQL block to debug utPLSQL test" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/debug_utplsql_test_anonymous_block.png" /></p>
 <p>The initialization timeout for the realtime reporter is increased to 1 hour. The overall timeout is left to the default value of 4 hours. So you have enough time to step through the PL/SQL code and analyse it. Press the <code>Stop</code> button at any time to cancel the test run.</p>
-<p><img alt="Stop utPLSQL test run" src="/images/debug_utplsql_test_stop.png" /></p>
+<p><img alt="Stop utPLSQL test run" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/debug_utplsql_test_stop.png" /></p>
 <h3 id="code-coverage">Code coverage...<a class="headerlink" href="#code-coverage" title="Permanent link">&para;</a></h3>
 <p>In the Connections window, select a connection or one or more packages for a code coverage report.</p>
 <p>In the dialog you can set some parameters. If you run code coverage for a few chosen packages or from the PL/SQL editor the objects to be included are determined according the object dependencies in the Oracle data dictionary.</p>
-<p><img alt="Code coverage dialog" src="/images/code_coverage_dialog.png" /></p>
+<p><img alt="Code coverage dialog" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/code_coverage_dialog.png" /></p>
 <p>Press <code>Run</code> to produce the code coverage process in the background. You may minimize or close the dialog. To abort the process, press <code>Cancel</code>.</p>
 <p>The HTML report is shown in your default browser.</p>
-<p><img alt="Code coverage report" src="/images/code_coverage_report_all_files.png" /></p>
+<p><img alt="Code coverage report" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/code_coverage_report_all_files.png" /></p>
 <h3 id="generate-utplsql-test">Generate utPLSQL test<a class="headerlink" href="#generate-utplsql-test" title="Permanent link">&para;</a></h3>
 <h4 id="based-on-existing-code">Based on existing code<a class="headerlink" href="#based-on-existing-code" title="Permanent link">&para;</a></h4>
 <p>Select a package, type, function or procedure to build a utPLSQL test package skeleton. The generated package compiles and executes, but still needs some rework.</p>
-<p><img alt="Generate utPLSQL test" src="/images/generate_utplsql_test.png" /></p>
+<p><img alt="Generate utPLSQL test" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/generate_utplsql_test.png" /></p>
 <h4 id="from-scratch">From scratch<a class="headerlink" href="#from-scratch" title="Permanent link">&para;</a></h4>
 <ol>
 <li>Press the button <code>Create code templates</code> in the preferences</li>
 <li>Type <code>ut_</code> in the Worksheet or a PL/SQL editor and press <code>Ctrl-Space</code> to get the list of a utPLSQL code templates</li>
 <li>Press <code>Return</code> to paste a code template at the current cursor position</li>
 </ol>
-<p><img alt="Generate utPLSQL test" src="/images/generate_utplsql_test_from_template.png" /></p>
+<p><img alt="Generate utPLSQL test" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/generate_utplsql_test_from_template.png" /></p>
 <h3 id="snippets">Snippets<a class="headerlink" href="#snippets" title="Permanent link">&para;</a></h3>
 <p>Import utPLSQL snippets for annotations and expectations via the the <code>Import Snippets</code> button of the utPLSQL <a href="#preferences">preferences dialog</a>.</p>
 <p>Insert the snippets by drag &amp; drop into your code.</p>
 <h4 id="annotations">Annotations<a class="headerlink" href="#annotations" title="Permanent link">&para;</a></h4>
 <p>Annotations are used in the package specification for various test configurations.</p>
-<p><img alt="utPLSQL Annotations" src="/images/snippets_annotations.png" /></p>
+<p><img alt="utPLSQL Annotations" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/snippets_annotations.png" /></p>
 <h4 id="expectations">Expectations<a class="headerlink" href="#expectations" title="Permanent link">&para;</a></h4>
 <p>Expectations are used in the package body to compare actual with expected results.</p>
-<p><img alt="utPLSQL Expectations" src="/images/snippets_expectations.png" /></p>
+<p><img alt="utPLSQL Expectations" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/snippets_expectations.png" /></p>
 <h3 id="preferences">Preferences<a class="headerlink" href="#preferences" title="Permanent link">&para;</a></h3>
 <p>Set your preferences to change the behaviour of utPLSQL within SQL Developer.</p>
-<p><img alt="Preferences" src="/images/preferences.png" /></p>
+<p><img alt="Preferences" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/preferences.png" /></p>
 <h3 id="oddgen-integration">oddgen integration<a class="headerlink" href="#oddgen-integration" title="Permanent link">&para;</a></h3>
 <p>utPLSQL for SQL Developer implements the <a href="https://www.oddgen.org/java-interface/">OddgenGenerator2 interface</a> to</p>
 <ul>
@@ -1682,10 +1682,10 @@ <h3 id="oddgen-integration">oddgen integration<a class="headerlink" href="#oddge
 <p>The use of <a href="https://www.oddgen.org/">oddgen for SQL Developer</a> is optional.</p>
 <h4 id="run-utplsql-test_1">Run utPLSQL test<a class="headerlink" href="#run-utplsql-test_1" title="Permanent link">&para;</a></h4>
 <p>utPLSQL can run tests based on suitepaths and suites. The next screenshot shows the generated run command for two selected suitepaths.</p>
-<p><img alt="Generate utPLSQL test" src="/images/oddgen_run_utplsql_test.png" /></p>
+<p><img alt="Generate utPLSQL test" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/oddgen_run_utplsql_test.png" /></p>
 <h4 id="generate-utplsql-test_1">Generate utPLSQL test<a class="headerlink" href="#generate-utplsql-test_1" title="Permanent link">&para;</a></h4>
 <p>Use oddgen to generate utPLSQL test package skeletons. When generating to files, a file for each package specification and package body is created.</p>
-<p><img alt="Generate utPLSQL test" src="/images/oddgen_generate_utplsql_test.png" /></p>
+<p><img alt="Generate utPLSQL test" src="https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/oddgen_generate_utplsql_test.png" /></p>
 <h2 id="releases">Releases<a class="headerlink" href="#releases" title="Permanent link">&para;</a></h2>
 <p>Binary releases are published <a href="https://github.com/utPLSQL/utPLSQL-SQLDeveloper/releases">here</a>.</p>
 <h2 id="installation">Installation<a class="headerlink" href="#installation" title="Permanent link">&para;</a></h2>
@@ -1775,7 +1775,7 @@ <h2 id="license">License<a class="headerlink" href="#license" title="Permanent l
     <span class="md-icon" title="Last update">
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg>
     </span>
-    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime" title="August 3, 2026 11:21:48 UTC">August 3, 2026 11:21:48</span>
+    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime" title="August 3, 2026 14:13:59 UTC">August 3, 2026 14:13:59</span>
   </span>