The work is still far from finished. I made some of the tests more easy to run, both others were just ported as is. So still some work there.
I was already thinking of improving the question. Allowing a clean quit from the question is a good one, although capturing ctrl-c and still generating the report might also be worth investigating (especially if the test hangs without a question). For the tests that determine whether they fail based on user input I also want to add a confirmation question. It might be that you accidentally did the wrong thing and you want to try again. Also by default logging to file should be enabled. Rob Op woensdag 20 mei 2015 06:57:36 UTC+2 schreef claudio canepa: > > > > On Sat, May 9, 2015 at 8:09 AM, Rob <[email protected] <javascript:>> > wrote: > >> Hi all, >> >> For pyglet 1.3.x I've been working on a new test framework >> > > ... > > The interactive tests seems to flow much better from the POV of 'user > testing', thanks for your work. > > Question: while running the interactive tests I got > > """ > tests.interactive.image.test_buffer_copy > (unittest.loader.ModuleImportFailure) . > .. ERROR > tests.interactive.image.test_buffer_saving > (unittest.loader.ModuleImportFailure) > ... ERROR > """ > > I wanted to see some details about the error, surely they were captured > somewhere. Being late I issued a ctrl-c to quit the test runner, supposing > a log would be left behind. No log found. > > Shouldn't the logging be progressive and be on by default ? > > And maybe change in the Q&A > Passed [Y/n]: > to > Passed[Y/n](q to quit): > > to allow a clean exit ? > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
