Cool. I think however it maybe the dialog itself that's the problem, not so much the testing in general.
Non of the other dialogs appear to fail. I actually took Padre::Wx::Dialog::SpecialValues out of the testing and it passed fine. I had a bit of a go a rewriting the dialog, but failed dismally.. :( > My little contribution to the effort is that I fixed the smoke testing > script so it will > use RELEASE_TESTING=1 and AUTOMATED_TESTING=1 and report when the test fails > > Gabor > > On Sun, Mar 21, 2010 at 3:44 AM, Adam Kennedy > <[email protected]> wrote: > > If we were to look at some kind of medium-term solution, one thing we > > might be able to do is to create a mechanism for Padre to flush open > > files and close opened tools. > > > > Then we could spawn a new Padre, rename the tests to a slightly > > different name, and then "do $file" the tests sequentially so they all > > run under a single process. > > > > Adam K > > > > On 21 March 2010 10:16, Peter Lavender <[email protected]> wrote: > >> Hi Everyone, > >> > >> I'm running testing under RELEASE_TESTING=1 and seeing failures. > >> > >> These are logged as tickets: > >> > >> http://padre.perlide.org/trac/ticket/902 > >> http://padre.perlide.org/trac/ticket/903 > >> > >> Both tests fail with this error: > >> > >> got: 'Padre->new has not been called yet at > >> /home/pete/Padre/trunk/Padre/blib/lib/Padre/Current.pm line 187 > >> > >> > >> I think it means we need to instantiate Padre to run this test due to > >> further interaction within the IDE's increasing more complex and dependant > >> classes ( I hope I'm making sense here! ). > >> > >> I think I've seen this same sort of error that was fixed by rhebus here: > >> > >> http://padre.perlide.org/trac/ticket/846 > >> > >> > >> Given the increased complexity with Padre now having deeper connections to > >> various parts of the application is there a way to simply starting > >> instances > >> of Padre so the various testing of components can be done with out a lot of > >> duplicate boiler plate? > >> > >> Pete. > _______________________________________________ > Padre-dev mailing list > [email protected] > http://mail.perlide.org/mailman/listinfo/padre-dev
_______________________________________________ Padre-dev mailing list [email protected] http://mail.perlide.org/mailman/listinfo/padre-dev
