Roundup Robot added the comment:
New changeset c818c215f1a4 by Terry Jan Reedy in branch '3.3':
Issue #18103: Update README.txt and test_idle to describe and run gui tests.
http://hg.python.org/cpython/rev/c818c215f1a4
--
nosy: +python-dev
___
Python
Roundup Robot added the comment:
New changeset 0767363a0393 by Terry Jan Reedy in branch '2.7':
Issue #18103: Update README.txt and test_idle to describe and run gui tests.
http://hg.python.org/cpython/rev/0767363a0393
--
___
Python tracker
Terry J. Reedy added the comment:
While I have not committed any gui tests, the patch is based on experiments
with a couple of temporary files.
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker
Terry J. Reedy added the comment:
Must mention that 'support' was 'test_support' in 2.7.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
___
Changes by R. Jayakrishnan raaj...@gmail.com:
--
nosy: +JayKrish
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
___
___
Python-bugs-list
Changes by Phil Webster webster.p...@gmail.com:
--
nosy: +philwebster
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
___
___
Python-bugs-list
R. David Murray added the comment:
Oh, actually I do know why that is. It is because requires is called from
test_main in test_urllibnet, which unittest bypasses. So if you are calling it
in particular tests, then I presume that will be an issue for the unittest case.
--
Terry J. Reedy added the comment:
I should have explicitly said 'all test methods in one test file'.
I included ' caller is __main__' in the requires 'pass' condition. My first
question was only about, for instance, running test_grep from the 'if __name__
...' part of GrepDialog, For that, I
Terry J. Reedy added the comment:
The basic question for this issue is whether to segregate gui tests in a
separate directory (idle_test_gui?) and run them with a separate
test_idle_gui.py? or to sprinkle gui test cases throughout the test suite,
perhaps one to each test_idle/text_xxx.py
Ned Deily added the comment:
Individual test cases are only seen if you run regrtest (-m test) in verbose
mode (-v). There are many test cases that are akipped in the standard library,
depending on platform and -u options, and you normally don't see them (without
-v). So mixing
Terry J. Reedy added the comment:
Thanks. That still leaves the problem of getting all tests to run during
development when running them with unittest. Calling requires('gui') passes
when (_is_gui_available() and (caller is __main__ or 'gui' in use_resources)).
Use_resources is normally set
Ned Deily added the comment:
Why not just run the tests under regrtest like all other standard library
tests? From the build directory, you could use something like (Windows may be
a bit different):
./python.exe -m test -h # to get regrtest options help
./python.exe -m test -ugui -v
Nick Coghlan added the comment:
Indeed, I think the most sensible course here is to require the use of regrtest
to run the GUI tests. Our other resource-dependent tests all fall into that
category already.
If the stdlib unittest provided a resource system, we'd rewrite the regrtest
resource
Ned Deily added the comment:
Terry: FYI, I just noticed the languishing patches in Issue4343 which *might*
be of some use here.
--
nosy: +ned.deily
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
Terry J. Reedy added the comment:
Thanks Ned. I commented on the issue. The code in the proposed function will
fix one of the two problems with tkinter.Variable that I noted in #18131. I can
imagine there might be situations in which it would also be useful for testing,
as GP claims.
Terry J. Reedy added the comment:
My experiments and some web postings indicate that if a tkinter class has a
master or parent option, it may not really be an option, regardless of what our
docs imply. If tkinter.Tk is called either directly or indirectly, the graphics
system is initiated and
Changes by Todd Rovito rovit...@gmail.com:
--
nosy: +Todd.Rovito
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
___
___
Python-bugs-list
New submission from Terry J. Reedy:
This is a follow-up to #15392, which created the Idle test framework. The
similar endpoint for this issue will be a framework for tests that require a
gui resource, at least one prototype test file, and documentation of Idle
practice. At the moment,
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
___
___
Terry J. Reedy added the comment:
I opened #18104 for the human-required gui tests described in the last
paragraph above.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18103
___
20 matches
Mail list logo
