incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #355: Run Trac test suite against product environments - after #115 #288
Date Thu, 17 Jan 2013 21:00:50 GMT
#355: Run Trac test suite against product environments - after #115 #288
---------------------------+------------------------------------
  Reporter:  olemis        |      Owner:  olemis
      Type:  task          |     Status:  accepted
  Priority:  major         |  Milestone:
 Component:  multiproduct  |    Version:
Resolution:                |   Keywords:  environment testing QA
---------------------------+------------------------------------
Description changed by olemis:

Old description:

> Apache™ Bloodhound inherits Trac functionality . By design the same
> behavior is expected for built-in components while running against
> product environments , and thereby Trac test suite should run without any
> failures if the global environment is replaced by a prodcut environment .
>
> This ticket is for translating Trac test cases to make them run against
> product environments (i.e. test setup) , but without modifying the
> assertions . Some minor differences might still be identified in product
> context and , if that is the case then there are two options :
>
>   1. write new test cases for product-specific features
>   2. update existing test case when product-specific
>     behavior is slightly different

New description:

 Apache™ Bloodhound inherits Trac functionality . By design the same
 behavior is expected for built-in components on top of product
 environments , and thereby Trac test suite should run without any failures
 if the global environment is replaced by a product environment .

 This ticket is for translating Trac test cases to make them run against
 product environments (i.e. test setup) , but without modifying the
 assertions . Some minor differences might still be identified in product
 context and , if that is the case then there are two options :

   1. write new test cases for product-specific features
   2. update existing test case when product-specific
     behavior is slightly different

--

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/355#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message