working example

[Veritogen]

Description

Fixes #77

Type of change

• [x] New feature (non-breaking change which adds functionality)

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
• [x] 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)
• [x] 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 (If there is none yet, create one !)
• [x] I have updated the changelog
• [ ] I have labeled my PR using appropriate tags (in particular using status labels like Status: Code Review Needed, Business: Test Needed or Status: In Progress if you are still working on the PR)

@js-dieu I'd be grateful for your input (also on the questions I posed in the issue mentioned above).

[Veritogen]

@js-dieu due to the effort of my colleague @lhpt2 we now have the feature fully tested and would like to merge changes that introduce a postgres db handler to pytest-monitor. Are there any steps we didn't to for a review? Unfortunately, I can't set the labels as expected in the PR checklist.

[Veritogen]

@js-dieu we also didn't set a release in the changelog.rst and just added "to be discussed". Will you set the release number or should we add something there?

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
2 Security Hotspots

See analysis details on SonarCloud

[lhpt2]

Notice: The quality gate failed because of literal passwords for the testing environment (which should not be a security issue as its only for testing purposes)