Clarify key rotations test cases by using keywords

[MVrachev]

Description of the changes being introduced by the pull request:

As I mentioned in my comment here #1607 (comment) while I was reviewing #1635 it was a little hard for me to remember the placement of the arguments for RootVersion considering they are 15 root rotations tested and the dataset becomes a larger piece of code.

That's why I suggest using keywords whenever possible to do that without splitting the RootVersion instance creation into two lines.

Signed-off-by: Martin Vrachev mvrachev@vmware.com

Please verify and check that the pull request fulfills the following
requirements:

• The code follows the Code Style Guidelines
• Tests have been added for the bug fix or new feature
• Docs have been added for the bug fix or new feature

[coveralls]

Pull Request Test Coverage Report for Build 1448985910

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+1.1%) to 98.571%

---

Totals
Change from base Build 1426058326:	1.1%
Covered Lines:	3116
Relevant Lines:	3129

---

💛 - Coveralls

[MVrachev]

#1659 was merged and I updated the pr to use keywords in all test cases.
@jku do you think I should rename res back to results and sigs back to signatures?

[jku]

LGTM. Is black going to accept these without complaints when you enable black?

[MVrachev]

Ohh... I forgot to run black on that change.
It's complaining...
I disabled black with # fmt: off for the test cases and then enabled it again with # fmt: on after them.

[coveralls]

Pull Request Test Coverage Report for Build 1393945892

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+1.1%) to 98.54%

---

Totals
Change from base Build 1390970499:	1.1%
Covered Lines:	3116
Relevant Lines:	3129

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 1393945892

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+1.1%) to 98.54%

---

Totals
Change from base Build 1390970499:	1.1%
Covered Lines:	3116
Relevant Lines:	3129

---

💛 - Coveralls