Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup seemingly unnecessary complexity around TestAssemblySettingsProvider #4951

Closed

Conversation

Youssef1313
Copy link
Member

@Youssef1313 Youssef1313 commented Feb 10, 2025

No description provided.

@Youssef1313 Youssef1313 marked this pull request as draft February 10, 2025 09:03
@Youssef1313 Youssef1313 marked this pull request as ready for review February 10, 2025 09:48
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.91%. Comparing base (b9cef47) to head (f9b90fd).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4951   +/-   ##
=======================================
  Coverage   63.90%   63.91%           
=======================================
  Files         600      600           
  Lines       35986    36035   +49     
=======================================
+ Hits        22998    23030   +32     
- Misses      12988    13005   +17     
Flag Coverage Δ
Debug 63.91% <100.00%> (+<0.01%) ⬆️
integration 60.23% <100.00%> (-0.01%) ⬇️
production 63.91% <100.00%> (+<0.01%) ⬆️
unit 63.90% <100.00%> (-0.01%) ⬇️

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

Files with missing lines Coverage Δ
...Test.TestAdapter/Execution/TestExecutionManager.cs 66.16% <100.00%> (+4.22%) ⬆️

... and 10 files with indirect coverage changes


try
{
sourceSettingsProvider = isolationHost.CreateInstanceForType(
Copy link
Member Author

Choose a reason for hiding this comment

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

We previously were creating an instance of TestAssemblySettingsProvider in a separate AppDomain, but we did "nothing" with it other than a null check. Then we simply call TestAssemblySettingsProvider.GetSettings

@Youssef1313
Copy link
Member Author

Replacing with #4952

@Youssef1313 Youssef1313 deleted the dev/ygerges/cleanup-TestAssemblySettingsProvider branch February 10, 2025 11:55
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.

2 participants