Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Tests | Split MultipleResultsTest, clean up console logging#3060

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
benrr101 merged 8 commits intodotnet:mainfromedwardneal:tests/console-logging
Mar 6, 2025

Conversation

edwardneal
Copy link
Contributor

This starts to adjust the way the SqlClient tests use the console stdout. It contains two changes.

MultipleResultsTest rework

This was one large method. It would temporarily replace the console stdout, log to it, then manually perform a diff between the stdout and a file bundled with the project.

I've modified this, splitting the large method into three tests (ExecuteNonQuery, ExecuteReader, ExecuteScalar.) These tests are designed to prove the way that SqlClient handles informational messages, exceptions and result sets when MARS is enabled.

Console stdout rework

I've noticed a few instances where standard output from the TDS servers get mixed in with the test results logged in the CI pipeline. This output isn't useful, even when the tests fail; I've disabled it in a few areas.

MichelZ reacted with thumbs up emojibenrr101 reacted with rocket emoji
@@ -76,7 +76,6 @@ public void CustomActiveDirectoryProviderTest_AppClientId_DeviceFlowCallback()

private Task CustomDeviceFlowCallback(DeviceCodeResult result)
Copy link
Contributor

Choose a reason for hiding this comment

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

It would help readability if we remove this method. It's not doing anything useful now that the logging is removed.

edwardneal reacted with thumbs up emoji
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Thanks, I've removed it. Can you trigger another CI run please?

@mdaigle
Copy link
Contributor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@codecovCodecov
Copy link

codecovbot commentedFeb 20, 2025
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.21%. Comparing base(0be2756) to head(f085005).
Report is 18 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (0be2756) and HEAD (f085005). Click for more details.

HEAD has 1 upload less than BASE
FlagBASE (0be2756)HEAD (f085005)
addons10
Additional details and impacted files
@@            Coverage Diff             @@##             main    #3060      +/-   ##==========================================- Coverage   72.81%   66.21%   -6.61%==========================================  Files         282      276       -6       Lines       59112    58802     -310     ==========================================- Hits        43045    38933    -4112- Misses      16067    19869    +3802
FlagCoverage Δ
addons?
netcore69.17% <ø> (-6.35%)⬇️
netfx64.86% <ø> (-6.28%)⬇️

Flags with carried forward coverage won't be shown.Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report?Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@benrr101benrr101 left a comment

Choose a reason for hiding this comment

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

This is awesome, I love anything that breaks up complicated tests and cleans up the console output on the tests. 🚀

Would love to see the few comments I made addressed, but I also won't hold things up if you don't want to address them.

@benrr101
Copy link
Contributor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@benrr101benrr101 merged commit87b5435 intodotnet:mainMar 6, 2025
123 checks passed
@edwardnealedwardneal deleted the tests/console-logging branchMarch 6, 2025 19:52
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@benrr101benrr101benrr101 approved these changes

@mdaiglemdaiglemdaigle approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@edwardneal@mdaigle@benrr101

[8]ページ先頭

©2009-2025 Movatter.jp