Skip to content

Fix: Failed unit tests - #46

Open
Mult1pers wants to merge 6 commits into
devfrom
test/issue-42
Open

Fix: Failed unit tests#46
Mult1pers wants to merge 6 commits into
devfrom
test/issue-42

Conversation

@Mult1pers

@Mult1pers Mult1pers commented Aug 10, 2026

Copy link
Copy Markdown

dev

JIRA

Code reviewers

Second Level Review

  • @github_username

Summary of issue

Unit tests could fail without GitHub Actions correctly reporting the failure.

Summary of change

Fixed GitHub Actions to correctly handle unit test execution and failure reporting.

Testing approach

Verified GitHub Actions workflow and SonarCloud Quality Gate.

CHECK LIST

  • СI passed
  • Сode coverage >=95%
  • PR is reviewed manually again (to make sure you have 100% ready code)
  • All reviewers agreed to merge the PR
  • I've checked new feature as logged in and logged out user if needed
  • PR meets all conventions

Comment thread .github/workflows/build.yml Fixed
Comment thread .github/workflows/build.yml Fixed
@Mult1pers Mult1pers changed the title Test to verify fail Fix: Failed unit tests Aug 10, 2026

@DrFaust555 DrFaust555 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dotnet-version: 10.0.x → 6.0.x reverts #32. This branch is based on that merge commit, and the solution targets net10.0 — the build only stayed green because the runner picked up an SDK 10 on its own (bin\Release\net10.0 in the log). Please drop this line from the diff.

The begin rewrite lost /d:sonar.coverage.exclusions="/Persistence/Migrations/". Without it EF migrations count towards coverage and the number drops for no real reason — please add it back.

The Set SonarCloud Token step is now dead: >> $GITHUB_ENV is bash syntax and the step runs under pwsh, where $GITHUB_ENV is undefined — it does nothing in the log. Both sonar steps already get the token from env:, so delete the step; that also stops the secret from leaking into every later step's environment.

The blank line added to GetAllMainTeamHandlerTests.cs is left over from the failing-test experiment — please revert it so the PR only touches the workflow. Same for the trailing whitespace after the two sonarscanner steps.

Also, please fill in the description — the two CI run links are the whole evidence for this task and belong in it — assign reviewers, and move card #42 to To Review. For the next one, name the branch fix/42/failed-tests-do-not-drop-build: the convention is type//description, and this is a CI fix rather than tests.

skorpionreser
skorpionreser previously approved these changes Aug 21, 2026

@skorpionreser skorpionreser left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t see any issues. Before merging, please remove the extra spaces after with: on line 17.

@Mult1pers
Mult1pers requested a review from DrFaust555 August 21, 2026 16:25
Exlizardium
Exlizardium previously approved these changes Aug 22, 2026

@Exlizardium Exlizardium left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra space after with: is yet to be removed. Other than that all good

@Mult1pers
Mult1pers dismissed stale reviews from Exlizardium and skorpionreser via 98ac2b2 August 24, 2026 11:45
@sonarqubecloud

Copy link
Copy Markdown

@M1R4MI M1R4MI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra space on line 17 were removed. And the rest of the code looks good

@emil720a1 emil720a1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests cover the main scenarios, but the predicate assertions currently evaluate expressions only against matching entities, so an incorrect predicate such as entity => true could still pass. Please verify predicates against both matching and non-matching entities. Also, use different values for streetcodeId and categoryId to detect swapped fields, assert the returned DTO instead of only result.IsSuccess, add final newlines to the new files, and update the branch with the latest dev before the final test run.

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.

7 participants