gh-71339: Use new assertion methods in test_idle

[terryjreedy]

Revise 10 tests in 7 files, with 1 test split into 2.

• Issue: Additional assert methods for unittest #71339

[terryjreedy]

@serhiy-storchaka I did not merge in case there is some reason you did not make all these changes. Feel free to merge.

[serhiy-storchaka]

LGTM. I propose yet one change:

diff --git a/Lib/idlelib/idle_test/test_run.py b/Lib/idlelib/idle_test/test_run.py
index 83ecbffa2a1..7366a4b708c 100644
--- a/Lib/idlelib/idle_test/test_run.py
+++ b/Lib/idlelib/idle_test/test_run.py
@@ -426,7 +426,7 @@ def test_exceptions(self):
         ex.runcode('1/0')
         t, e, tb = ex.user_exc_info
         self.assertIs(t, TypeError)
-        self.assertTrue(isinstance(e.__context__, ZeroDivisionError))
+        self.assertIsInstance(e.__context__, ZeroDivisionError)
 
 
 if __name__ == '__main__':

[terryjreedy]

I will make a separate PR for old specialized methods. There are at least 20 assertEqual(something, None)s that could use 'assertIsNone'. And I found this in test_calltip.py line 334: self.assertIsNone(self.ct.active_calltip, None).

By the 'first one' do you mean the splitting of the condition? It seems that if the conjunction is correct then both separate conditions are correct. The difference is that any error message will be more specific.

[miss-islington-app]

Thanks @terryjreedy for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13.
🐍🍒⛏🤖

[bedevere-app]

GH-129237 is a backport of this pull request to the 3.13 branch.

[bedevere-app]

GH-129238 is a backport of this pull request to the 3.12 branch.