Skip to content

Commit 3bdd3c3

Browse files
committed
Modified readme in attempt to workaround the issue: mondeja/mkdocs-include-markdown-plugin#302
1 parent 7e2b244 commit 3bdd3c3

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

README.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -14,49 +14,49 @@ utPLSQL for SQL Developer extends Oracle's SQL Developer to
1414

1515
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.
1616

17-
![Run utPLSQL test](/images/run_utplsql_test.png)
17+
![Run utPLSQL test](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/run_utplsql_test.png)
1818

1919
### Debug utPLSQL test
2020

2121
Select the tests to debug, the same way you would if you were just running them, but select `Debug utPLSQL test...` in the context menu.
2222

2323
And then the PL/SQL Debugger is called for the generated, anonymous PL/SQL block.
2424

25-
![Anonymous PL/SQL block to debug utPLSQL test](/images/debug_utplsql_test_anonymous_block.png)
25+
![Anonymous PL/SQL block to debug utPLSQL test](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/debug_utplsql_test_anonymous_block.png)
2626

2727
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 `Stop` button at any time to cancel the test run.
2828

29-
![Stop utPLSQL test run](/images/debug_utplsql_test_stop.png)
29+
![Stop utPLSQL test run](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/debug_utplsql_test_stop.png)
3030

3131
### Code coverage...
3232

3333
In the Connections window, select a connection or one or more packages for a code coverage report.
3434

3535
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.
3636

37-
![Code coverage dialog](/images/code_coverage_dialog.png)
37+
![Code coverage dialog](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/code_coverage_dialog.png)
3838

3939
Press `Run` to produce the code coverage process in the background. You may minimize or close the dialog. To abort the process, press `Cancel`.
4040

4141
The HTML report is shown in your default browser.
4242

43-
![Code coverage report](/images/code_coverage_report_all_files.png)
43+
![Code coverage report](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/code_coverage_report_all_files.png)
4444

4545
### Generate utPLSQL test
4646

4747
#### Based on existing code
4848

4949
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.
5050

51-
![Generate utPLSQL test](/images/generate_utplsql_test.png)
51+
![Generate utPLSQL test](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/generate_utplsql_test.png)
5252

5353
#### From scratch
5454

5555
1. Press the button `Create code templates` in the preferences
5656
2. Type `ut_` in the Worksheet or a PL/SQL editor and press `Ctrl-Space` to get the list of a utPLSQL code templates
5757
3. Press `Return` to paste a code template at the current cursor position
5858

59-
![Generate utPLSQL test](/images/generate_utplsql_test_from_template.png)
59+
![Generate utPLSQL test](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/generate_utplsql_test_from_template.png)
6060

6161
### Snippets
6262

@@ -68,19 +68,19 @@ Insert the snippets by drag & drop into your code.
6868

6969
Annotations are used in the package specification for various test configurations.
7070

71-
![utPLSQL Annotations](/images/snippets_annotations.png)
71+
![utPLSQL Annotations](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/snippets_annotations.png)
7272

7373
#### Expectations
7474

7575
Expectations are used in the package body to compare actual with expected results.
7676

77-
![utPLSQL Expectations](/images/snippets_expectations.png)
77+
![utPLSQL Expectations](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/snippets_expectations.png)
7878

7979
### Preferences
8080

8181
Set your preferences to change the behaviour of utPLSQL within SQL Developer.
8282

83-
![Preferences](/images/preferences.png)
83+
![Preferences](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/preferences.png)
8484

8585
### oddgen integration
8686

@@ -95,13 +95,13 @@ The use of [oddgen for SQL Developer](https://www.oddgen.org/) is optional.
9595

9696
utPLSQL can run tests based on suitepaths and suites. The next screenshot shows the generated run command for two selected suitepaths.
9797

98-
![Generate utPLSQL test](/images/oddgen_run_utplsql_test.png)
98+
![Generate utPLSQL test](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/oddgen_run_utplsql_test.png)
9999

100100
#### Generate utPLSQL test
101101

102102
Use oddgen to generate utPLSQL test package skeletons. When generating to files, a file for each package specification and package body is created.
103103

104-
![Generate utPLSQL test](/images/oddgen_generate_utplsql_test.png)
104+
![Generate utPLSQL test](https://raw.githubusercontent.com/utPLSQL/utPLSQL-SQLDeveloper/main/images/oddgen_generate_utplsql_test.png)
105105

106106
## Releases
107107

0 commit comments

Comments
 (0)