Sonar test

[markpit]

JIRA link

Change description

Work checklist

• Tests added where applicable
• UI changes meet accessibility criteria

Merge instructions

We are committed to keeping commit history clean, consistent and linear. To achieve this, this commit should be structured as follows:

<type>[optional scope]: <description>

and contain the following structural elements:

• fix: a commit that patches a bug in your codebase (this correlates with PATCH in semantic versioning),
• feat: a commit that introduces a new feature to the codebase (this correlates with MINOR in semantic versioning),
• BREAKING CHANGE: a commit that has a footer BREAKING CHANGE: introduces a breaking API change (correlating with MAJOR in semantic versioning). A BREAKING CHANGE can be part of commits of any type,
• types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
• footers other than BREAKING CHANGE: <description> may be provided.

[chsonarqubeprchecks]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication