Fix #1897: Add tests for ItemSelectionInputDoesNotContainAtLeastOneOfRuleClassifierProvider

[fsharpasharp]

Explanation

Fixes #1897 by adding tests for ItemSelectionInputDoesNotContainAtLeastOneOfRuleClassifierProvider. I copied ItemSelectionInputContainsAtLeastOneOfRuleClassifierProviderTest and swapped the assertion values. This is possible since the original test file contains the tests for the negation of ItemSelectionInputDoesNotContainAtLeastOneOfRuleClassifierProvider.

Checklist

• The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
• The PR follows the style guide.
• The PR does not contain any unnecessary auto-generated code from Android Studio.
• The PR is made from a branch that's not called "develop".
• The PR is made from a branch that is up-to-date with "develop".
• The PR's branch is based on "develop" and not on any other branch.
• The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

[anandwana001]

You can setup ktlint to prevent such failures - https://github.com/oppia/oppia-android/wiki/Ktlint-Guide

[fsharpasharp]

Thanks @anandwana001, I'll use that for the future. It seems like the culprit is this line

DaggerItemSelectionInputDoesNotContainAtLeastOneOfRuleClassifierProviderTest_TestApplicationComponent.

Not sure if I can break the line. Any ideas?

[anandwana001]

It's a max length of char in a line error. Please check the above guide to fix the issue.

[fsharpasharp]

Okay! I added the // ktlint-disable max-line-length comment to the line.

[anandwana001]

Thanks @fsharpasharp
Nit fix suggested

[anandwana001]

ItemSelectionInputDoesNotContainAtLeastOneOfRuleClassifierProviderTest It should be the name of the file.

[fsharpasharp]

Renamed it.

[anandwana001]

@fsharpasharp The suggestions should be resolved by the author as the reviewer needs to check if the suggested changes are correct or need any further modification.

[anandwana001]

@fsharpasharp closing this PR as force push is not allowed.