Looking more into this, it's possible to guide the test system by modifying a copy of tests/plan.txt, then you feed it as a parameter to test.py with the --plan= parameter. Nice. My backports branch isn't too far from passing the tests.
Tomorrow I'll do my best to match parity with the 1.1.3 release's testing with my backports. If I can do that, I will merge them into the 1.1-maintenance branch at that point. So far that's looking pretty straightforward, as nobody else has committed to it since I branched. -b On Aug 17, 7:45 pm, Ben Smith <[email protected]> wrote: > Hey folks. > > I'm unable to get through the tests on 1.1.3, 1.1-maintenance head, > and my own backport branch. Are others having this problem? I'm on > vista 64, python 2.6. > > I'm able to get to the test labelled: "Test that close event works > correctly." but I can't close the program by pressing esc or closing > the window. I have to control-c to exit, and at that point I can't > run further tests. > > On the 1.1.3 tag and on 1.1-maintenance, an earlier test also fails > with the esc key, though closing the window works. It's titled: "Test > that mouse cursor can be set to a platform-dependent image." The > cursor does change, just can't close with esc. > > Also, is there any fully automated testing process? I realize that > some tests must have visual inspection to verify, but having a batch > of tests that can be run without interaction would be nice - I'm sure > I don't want to run this visual test every time. > > I also get a bunch of assertions in the graphics.IMMEDIATE tests, > starting with this one(and there are 40 more): > INFO:root:Testing graphics.IMMEDIATE. > INFO:root:Begin unit tests for graphics.IMMEDIATE > ERROR:root:Failure in graphics.IMMEDIATE > ERROR:root:Traceback (most recent call last): > File "..\tests\graphics\IMMEDIATE.py", line 42, in test_v2f > self.generic_test('v2f', v2f_data) > File "..\tests\graphics\IMMEDIATE.py", line 35, in generic_test > self.check(v_data, vertices, n_v) > File "..\tests\graphics\IMMEDIATE.py", line 20, in check > (e, r)) > AssertionError: Feedback array is in error: 0.022058823529411766, > 2.3382344245910645 > > -b --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
