Linux users: please run gui tests

[Terry Reedy]

On 8/7/2015 1:01 PM, Laura Creighton wrote:
> In a message of Fri, 07 Aug 2015 17:34:54 +0200, Peter Otten writes:
>> Run
>>
>> $ python3 -m test -ugui -v test_tk
>>
>> (That way the unittest framework will see the -v option)
>
> Aha, I didn't understand that.  Thank you.
>
>> Note that there are lines like
>>
>> # possible namespace for /home/lac/src/accounting/test
>>
>> in your python3 -v output that indicate that there may still be too much in
>> your PYTHONPATH.
>
> It's now "" for this test.
>
> I get 3 failures, as follows (I trimmed the rest of the ok ones).
>
> = CPython 3.4.3+ (default, Jul 28 2015, 13:17:50) [GCC 4.9.3]
> ==   Linux-3.16.0-4-amd64-x86_64-with-debian-stretch-sid little-endian
> ==   hash algorithm: siphash24 64bit
> ==   /tmp/test_python_7974
> Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=0)
>
> test_default (tkinter.test.test_tkinter.test_variables.TestBooleanVar) ... FAIL
> test_get (tkinter.test.test_tkinter.test_variables.TestBooleanVar) ... FAIL
> test_set (tkinter.test.test_tkinter.test_variables.TestBooleanVar) ... FAIL
>
> ======================================================================
> FAIL: test_default (tkinter.test.test_tkinter.test_variables.TestBooleanVar)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "/usr/lib/python3.4/tkinter/test/test_tkinter/test_variables.py", line 163, in test_default
>        self.assertIs(v.get(), False)
>        AssertionError: 0 is not False
>
> ======================================================================
> FAIL: test_get (tkinter.test.test_tkinter.test_variables.TestBooleanVar)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "/usr/lib/python3.4/tkinter/test/test_tkinter/test_variables.py", line 167, in test_get
>        self.assertIs(v.get(), True)
>        AssertionError: 1 is not True
>
> ======================================================================
> FAIL: test_set (tkinter.test.test_tkinter.test_variables.TestBooleanVar)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "/usr/lib/python3.4/tkinter/test/test_tkinter/test_variables.py", line 186, in test_set
>        self.assertEqual(self.root.globalgetvar("name"), true)
>        AssertionError: 42 != 1
>
> ----------------------------------------------------------------------
> Ran 660 tests in 3.901s
>
> FAILED (failures=3)
> 1 test failed:
>      test_tk

The only thing I found on the tracker is
https://bugs.python.org/issue20067
I suspect that this is more an issue with the tests, which are somewhat 
new, than tkinter itself.  In any case, my personal concern is whether 
adding ttk to Idle creates a problem, and those two tests passes.  Thank 
you for trying.



-- 
Terry Jan Reedy