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

FunctionalTests: drop unused negative runner methods #444

Merged
merged 1 commit into from
Oct 5, 2020

Conversation

chrisd8088
Copy link
Collaborator

We can prune the various negative "should fail" and "should not" methods from the FileSystemRunner classes as these are no longer utilized by any tests.

These methods were previously used by the BasicFileSystemTests and MoveRenameFolderTests, which were removed in commit d748084.

Three additional methods could also be removed from these runner classes, namely FileSize(), ReplaceFile(), and RenameDirectory(). I left them in because it seemed like they might be more obviously useful in the future than the "negative" methods.

OTOH these three additional unused methods could also be pruned now and then resurrected from Git history if they are ever needed again. If the latter is preferred, I can add commit d32582c to this PR to also drop them; just let me know either way.

We can prune the various negative "should fail" and "should not"
methods from the FileSystemRunner classes as these are no longer
utilized by any tests.

These methods were previously used by the BasicFileSystemTests and
MoveRenameFolderTests, which were removed in commit
d748084.
@chrisd8088 chrisd8088 merged commit fba4343 into microsoft:main Oct 5, 2020
@chrisd8088 chrisd8088 deleted the prune-unused-code branch October 5, 2020 17:04
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.

3 participants