Skip to content

ci: leave the end-to-end suite out of the SonarCloud coverage - #2210

Merged
ludomikula merged 1 commit into
devfrom
sonar-exclude-e2e
Nov 22, 2026
Merged

ludomikula merged 1 commit into
devfrom
sonar-exclude-e2e

Conversation

@ludomikula

Copy link
Copy Markdown
Collaborator

Proposed changes

Exclude e2e from sonarqube.

Types of changes

What types of changes does your code introduce to Lowcoder?
Put an x in the boxes that apply.

  • Bugfix (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)
  • Documentation Update (if none of the other choices apply)

Checklist

You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put an x in the boxes that apply.

  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Further comments

n/a

…ar-text protocol checks

The Playwright suite in e2e/ is test code that runs against a container
stack, so it has no coverage report, and its http:// uses are container-internal
addresses and a URL parsing base. Exclude e2e/** from coverage and ignore only
rule S5332 there.

Claude-Session: https://claude.ai/code/session_015KPtHMWb4EyLtt5JPr1vtb
@ludomikula
ludomikula merged commit d393b46 into dev Nov 22, 2026
4 of 5 checks passed
@ludomikula
ludomikula deleted the sonar-exclude-e2e branch November 22, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant