[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Upstream bugs... (Qt)
From:       Thiago Macieira <thiago () kde ! org>
Date:       2009-11-27 14:44:35
Message-ID: 200911271544.36172.thiago () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Em Sexta-feira 27 Novembro 2009, Ã s 14:33:58, Parker Coates escreveu:
> Okay, this makes it clear that I don't really know what a testcase is
> supposed to be. I had assumed they were just examples to demonstrate
> that the issue exists and maybe show a couple of workarounds. But
> obviously they need to be more than that to plug them into an
> automatic system. Are they supposed to be actual QTest tests? Are
> there special rules for writing them? How does the automatic test
> system work? If I report an intermittent rendering issue in QGV, can I
> realistically write a testcase? Is all of this documented somewhere
> and am I annoying you with questions for no good reason?

Examples are good enough, if we can tell from it what's wrong and what should 
have happened instead.

The best would be a QtTest testcase, preferrably a patch one of the existing 
unit tests in tests/auto in the Qt source tree. It's not always possible to 
write a testcase, I agree with you. In that case, a simple sample and an 
explanation is good enough.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]