On 12/07/2012 05:33 PM, Thiago Macieira wrote:
> On sexta-feira, 7 de dezembro de 2012 17.12.06, Jedrzej Nowacki wrote:
>>> I agree in theory, provided that the tests that do stress out the
>>> integration are close to complete testing. In practice, there's no way to
>>> tell whether the testing is
On sexta-feira, 7 de dezembro de 2012 17.12.06, Jedrzej Nowacki wrote:
> > I agree in theory, provided that the tests that do stress out the
> > integration are close to complete testing. In practice, there's no way to
> > tell whether the testing is enough, so I'd rather we keep full testing,
> >
> From: Jedrzej Nowacki
>Subject: Re: [Development] Running Qt auto-tests offscreen
>On Friday 7. December 2012 16.55.41 Thiago Macieira wrote:
>> On sexta-feira, 7 de dezembro de 2012 11.04.27, Samuel Rødal wrote:
>> > In the end, maybe we could even use this for
On Friday 7. December 2012 16.55.41 Thiago Macieira wrote:
> On sexta-feira, 7 de dezembro de 2012 11.04.27, Samuel Rødal wrote:
> > In the end, maybe we could even use this for a subset of the tests in
> > the CI system. In my opinion, with the current platform abstraction
> > layer we have in pla
On sexta-feira, 7 de dezembro de 2012 11.04.27, Samuel Rødal wrote:
> In the end, maybe we could even use this for a subset of the tests in
> the CI system. In my opinion, with the current platform abstraction
> layer we have in place in QtGui, it's unnecessary for most of the
> widgets tests to ac
Hello,
do you use the CI system as a way to run the auto-tests? Are you tired
of having to wait forever for the widgets auto-tests to run, at the same
time as they pop up a hundred windows and dialogs that steal the focus
and prevent you from doing any work? In that case I'm working on a
solut
