Open Stack

Examining the newly implemented test UUIDs, I found that there are 496 test
cases that have multiple test cases associated with same UUIDs.   These can
be categorized into 2 groups:

   A single UUID is associated to multiple test cases for different API
   versions.  Since we can only test one API version at a time, this will
   not be an issue for Refstack.  Example:
      tempest.api.volume.admin.test_volume_types_negative.VolumeTypesNegativeV2Test.test_create_with_nonexistent_volume_type
[gate,id-b48c98f2-e662-4885-9b71-032256906314]
      tempest.api.volume.admin.test_volume_types_negative.VolumeTypesNegativeV1Test.test_create_with_nonexistent_volume_type
[gate,id-b48c98f2-e662-4885-9b71-032256906314]

   A single UUID associates to multiple test cases for different features,
   protocols (IPv4 vs IPv6) ... In this case, it is very possible that we
   could invoke all tests on the same test run. Should these tests have
   different UUIDs? The issue is DefCore will define must-pass tests using
   test UUID.   In the example below since all 3 test cases have the same
   UUID, which would be the test cases that must pass? all 3? or just one
   of the 3?
      tempest.api.network.test_networks.NetworksTestJSON.test_list_networks_fields
[gate,id-6ae6d24f-9194-4869-9c85-c313cb20e080,smoke]
      tempest.api.network.test_networks.NetworksIpV6TestJSON.test_list_networks_fields
[gate,id-6ae6d24f-9194-4869-9c85-c313cb20e080,smoke]
      tempest.api.network.test_networks.NetworksIpV6TestAttrs.test_list_networks_fields
[gate,id-6ae6d24f-9194-4869-9c85-c313cb20e080,smoke]

A complete list of the 496 test cases can be found in
https://docs.google.com/spreadsheets/d/1mXeDNsJJJl93juzlNG9ccxSdO9ywqIeM-E2EJdvNImk/edit#gid=1273407686

Catherine Cuong Diep
High Performance On Demand Solutions
IBM Silicon Valley Laboratory, San Jose, California 95141
cdiep at us.ibm.com, Tel: (408) 463-4352  T/L: 543-4352
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/fits/attachments/20150304/0a0809d9/attachment.html>