#35 - Better handling of doctest item.

[js-dieu]

Description

Provide a better handling of doctest item. We keep executing them, but shunt the monitoring process for this kind of item. If no monitoring at all has been requested, the whole monitoring process is shunted.

Fixes #35

Type of change

Please delete options that are not relevant.

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes (not just the CI)
• ~[ ] Any dependent changes have been merged and published in downstream modules~
• [x] I have provided a link to the issue this PR adresses in the Description section above
• [ ] I have updated the changelog
• [x] I have labeled my PR using appropriate tags

Thanks for contributing! :pray:

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication