Actions

icon Post
text/html Subscribe
text/html Unsubscribe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qmtest] supporting unsupported tests


  • To: jtc@xxxxxxxxxxxxxxxxxx
  • Subject: Re: [qmtest] supporting unsupported tests
  • From: Stefan Seefeld <seefeld@xxxxxxxxxxxx>
  • Date: Wed, 29 Nov 2006 14:54:42 -0500

J.T. Conklin wrote:
> Hi folks,
> 
> We've moved our system to a second platform and some of the tests are
> appropriate for one system but not the other.  
> 
> What method is typically used to mark a test as not to be run for one
> platform?  Should I be thinking about having the test run but always
> pass (perhaps by replacing all my use of ExecTest and ShellCommandTest
> with subclasses that check a "platform type" property before either
> forwarding to the base class or always returning success), or is their
> a concept of a "UNTESTABLE" state separate from "PASS" and "FAIL".

I think the UNTESTED pseudo result is most suitable to indicate that.
However, in order for the  test database to generate such outcomes,
you either need a custom test database, or you need to make all your
tests depend on a common 'resource' that will fail on some platforms,
and thus cause dependent tests not to get run.
(Tests themselves are only able to set PASS or FAIL.)


Regards,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...