deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DTACLOUD-471) Need to cleanly skip CIMI Resource Metadata tests for unsupported capabilities
Date Wed, 20 Feb 2013 00:57:13 GMT

     [ https://issues.apache.org/jira/browse/DTACLOUD-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ronelle Landy resolved DTACLOUD-471.
------------------------------------

    Resolution: Fixed

Sent a patch to skip rmd tests for providers that don't support the rmd type under test: 
http://tracker.deltacloud.org/set/329
                
> Need to cleanly skip CIMI Resource Metadata tests for unsupported capabilities
> ------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-471
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-471
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: CIMI/Frontend
>            Reporter: Marios Andreou
>            Assignee: Ronelle Landy
>
> Context from rlandy via e-mail:
> If we run the resource metadata tests against any provider other than mock, rmd3_test.rb
and rmd4_test.rb will error out in the lines that determine the index of the capability under
test.
> Question is: do we need to write some protective code to avoid failures like:
> unless rmd_coll.json["resourceMetadata"][machine_index]["capabilities"].nil?() 
> unless rmd_coll.json["resourceMetadata"][machine_index]["capabilities"] <includes
the capability under test>
> run test ....
> or is it ok to assume that these tests can and will only be executed where the capabilities
exist?
> If we do need the protective code, the failures occur on line 38 in rmd3_test.rb and
line 40 in rmd4_test.rb - where we check for the index of the capability. Since this code
shows up before any it ... do ... end testpoints, using 'skip' is not suitable. Is it ok to
just add the unless lines above to the tests or is there a better (more ruby-stlyish) way
to skip the entire test?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message