[ https://issues.apache.org/jira/browse/DTACLOUD-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy closed DTACLOUD-471. ---------------------------------- Patch committed > 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 > Attachments: > 0003-CIMI-Tests-cleanly-skip-CIMI-Resource-Metadata-tests.patch > > > 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