-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Remove legacy API test that already have coverage and refactor code. #2015
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
Conversation
test/Microsoft.ML.Tests/ScenariosWithDirectInstantiation/TensorflowTests.cs
Outdated
Show resolved
Hide resolved
test/Microsoft.ML.Tests/ScenariosWithDirectInstantiation/IrisPlantClassificationTests.cs
Outdated
Show resolved
Hide resolved
Could you add the SymSGD test directly in this PR? It would be good to check that we can regain the test coverage of microsoft.ml.hallearners.dll and have a final number on the impact of this PR. #Resolved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleted all tests under test/Microsoft.ML.Tests/Scenarios/PipelineApi and removed SentimentPredictionTests.cs from test/Microsoft.ML.Tests/ScenariosWithDirectInstantiation because these tests already have equivalent tests that use new api under test/Microsoft.ML.Tests/Scenarios/Api/Estimators.
Verified the code coverage wasn't affected too much, its now at 68.94% vs 68.97% the difference is in the below dlls:
microsoft.ml.data.dll - 0.05%
microsoft.ml.entrypoints.dll - 0.18% (expected since legacy api calls into core entrypoints API)
microsoft.ml.fasttree.dll - 0.04%
microsoft.ml.hallearners.dll - 0.99% (This drop is coming from the removal of SymSGD test, will add one in another PR)
microsoft.ml.transforms.dll - 0.06%