I joined a workshop at EuroPython and I see definite awesomeness. The speaker also helped me find the hooks I need to add the customization I need for the interactive tests. I'll try to create a prototype later this week.
Rob Op maandag 20 juli 2015 18:06:01 UTC+2 schreef Richard Jones: > > Please, use the py.test! It's awesome :) > > On 20 July 2015 at 23:32, Rob <[email protected] <javascript:>> wrote: > >> Hi, >> >> As with a lot of functionality in Python, there is no need to create >> yourself what has already been created by others. That's why I am >> considering using one of the other test frameworks that give me this >> functionality for free. Would anybody be against using eg py.test for >> running the tests? I will of course include it in the extlibs so batteries >> are included ;-). >> >> Rob >> >> Op donderdag 21 mei 2015 22:09:11 UTC+2 schreef Rob: >>> >>> 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]> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/pyglet-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
