Skip to content

Commit 98ff13b

Browse files
Merge branch 'topic/doc' into 'master'
Move .png files to doc/media folder See merge request eng/ide/ada_language_server!2088
2 parents ac2bea1 + aee51e2 commit 98ff13b

File tree

6 files changed

+5
-5
lines changed

6 files changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ The extension provides a number of auto-detected tasks under the `/Terminal/Run
195195
predefined tasks are all prefixed by `ada:` and belong to the `ada` group.
196196
They can be used to build and run your program (`ada: Build current project` task) or launch external tools such as GNAT SAS, GNATprove and a few others.
197197

198-
<img src="doc/run-task-ada-tasks.png" width="500" alt="GNATtest Test Results"/>
198+
<img src="doc/media/run-task-ada-tasks.png" width="500" alt="GNATtest Test Results"/>
199199

200200
You can bind keyboard shortcuts to them by adding to the `keybindings.json` file:
201201

@@ -297,15 +297,15 @@ If you install GNATtest, the Ada & SPARK extension for VS Code will provide the
297297

298298
* Tests created with GNATtest will be loaded in the VS Code **Testing** view as follows.
299299

300-
<img src="doc/gnattest-test-tree.png" width="650" alt="GNATtest Test Tree"/>
300+
<img src="doc/media/gnattest-test-tree.png" width="650" alt="GNATtest Test Tree"/>
301301

302302
* Tests can be executed individually or in batch through the available buttons in the interface, or through the `Test: Run All Tests` command or related commands.
303303

304304
* Test execution always starts by executing the `ada: Build GNATtest test harness project` task to make sure that test executables are up to date.
305305

306306
* Test execution results are reflected in the test tree.
307307

308-
<img src="doc/gnattest-results.png" width="500" alt="GNATtest Test Results"/>
308+
<img src="doc/media/gnattest-results.png" width="500" alt="GNATtest Test Results"/>
309309

310310
#### Using multi-root workspaces for test development
311311

@@ -330,7 +330,7 @@ GNATcoverage coverage reports can be imported in VS Code as follows:
330330
2. Invoke the VS Code command `ada: GNATcoverage - Load an existing XML coverage report`
331331
3. Browse to the location of the GNATcoverage XML report and select the `index.xml` file
332332

333-
<img src="doc/gnatcov-report.png" width="1000" alt="GNATcoverage report in VS Code" />
333+
<img src="doc/media/gnatcov-report.png" width="1000" alt="GNATcoverage report in VS Code" />
334334

335335
Note that importing coverage reports does not require GNATcoverage to be installed. In particular, this enables a workflow where the coverage report is produced in CI and downloaded and imported into VS Code for visualization and analysis.
336336

@@ -349,7 +349,7 @@ The GNATtest integration in VS Code also supports running tests in coverage mode
349349
1. Invoke [GNATcoverage source coverage analysis](https://docs.adacore.com/live/wave/gnatdas/html/gnatdas_ug/gnatcov/cov_source.html)
350350
1. Load the GNATcoverage report into VS Code
351351

352-
<img src="doc/gnattest-gnatcov.png" width="1000" alt="GNATtest with GNATcoverage in VS Code" />
352+
<img src="doc/media/gnattest-gnatcov.png" width="1000" alt="GNATtest with GNATcoverage in VS Code" />
353353

354354
Integrating the steps of source instrumentation and test harness build into the test execution workflow allows for a quick feedback loop: run a test, observe results and coverage, edit the test or the tested code, repeat... In this context invoking the VS Code commands `Test: Rerun Last Run` and `Test: Rerun Last Run with Coverage` with their respective keyboard shortcuts can be valuable.
355355

File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)