Skip to content

Commit 2e052e2

Browse files
committed
use svg
1 parent 9843640 commit 2e052e2

File tree

2 files changed

+113
-5
lines changed

2 files changed

+113
-5
lines changed

src/content/docs/blog/2025-10-08-testing-your-algo-on-a-java-project.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ tags:
99
- infrastructure
1010
---
1111

12+
import ProcessSVG from './img/posts/2025-10-08-testing-your-algo-on-a-java-project/process.drawio.svg';
13+
1214
When developping algorithm on top of the Moose platform, we can easily hurt a wall during testing.
1315

1416
To do functional (and sometimes unit) testing, we need to work on a Moose model. Most of the time we are getting this model in two ways:
@@ -27,7 +29,7 @@ In order to avoid those drawbacks I will describe my way of managing such testin
2729

2830
The idea I had for testing callgraphs is to implement real java projects in a `resources` folder in the git of the project. Then, we can parse them when launching the tests and manipulate the produced model. This would ensure that we always have a model up to date with the latest version of Famix. If tests breaks, this means that our famix model evolved and that our project does not work anymore for this language.
2931

30-
![Process](./img/posts/2025-10-08-testing-your-algo-on-a-java-project/process.drawio.svg)
32+
<ProcessSVG className="svg-theme" />
3133

3234
## Basic setup
3335

0 commit comments

Comments
 (0)